Prv8 Shell
Server : Apache
System : Linux vps.urbanovitalino.adv.br 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64
User : urbanovitalinoad ( 1001)
PHP Version : 7.3.33
Disable Function : exec,passthru,shell_exec,system
Directory :  /proc/self/root/var/log/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : //proc/self/root/var/log/elevate-cpanel.log
* 10-04:30:51 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 10-04:30:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 10-04:30:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 10-04:30:53 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 10-04:30:53 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 10-04:30:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 10-04:31:12 (2925) [INFO] Checking if your system is up to date: 
* 10-04:31:12 (3361) [INFO] Running: /usr/bin/yum clean all
* 10-04:31:12 (3362) [INFO] 
* 10-04:31:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:31:13 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 10-04:31:13 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 10-04:31:13 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 10-04:31:13 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 10-04:31:13 (3372) [INFO]               : zabbix zabbix-non-supported
* 10-04:31:13 (3372) [INFO] Cleaning up list of fastest mirrors
* 10-04:31:13 (3372) [INFO] Other repos take up 3.7 M of disk space (use --verbose for details)
* 10-04:31:13 (3382) [INFO] 
* 10-04:31:13 (3361) [INFO] Running: /usr/bin/yum check-update
* 10-04:31:13 (3362) [INFO] 
* 10-04:31:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:31:14 (3372) [INFO] Determining fastest mirrors
* 10-04:31:19 (3372) [INFO]  * EA4: 208.100.0.204
* 10-04:31:19 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 10-04:31:19 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 10-04:31:19 (3372) [INFO]  * epel: mirror.dst.ca
* 10-04:31:19 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 10-04:31:44 (3372) [INFO] 
* 10-04:31:44 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 10-04:31:44 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 10-04:31:45 (3382) [INFO] 
* 10-04:31:45 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 10-04:31:45 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 10-04:31:45 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 10-04:31:45 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 10-04:31:46 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-10_04:31:46_modified_for_AlmaLinux_8.json
* 10-04:31:46 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 10-04:31:46 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 11-04:28:05 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 11-04:28:07 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 11-04:28:07 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 11-04:28:07 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 11-04:28:07 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 11-04:28:07 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 11-04:28:24 (2925) [INFO] Checking if your system is up to date: 
* 11-04:28:24 (3361) [INFO] Running: /usr/bin/yum clean all
* 11-04:28:24 (3362) [INFO] 
* 11-04:28:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:28:24 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 11-04:28:24 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 11-04:28:24 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 11-04:28:24 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 11-04:28:24 (3372) [INFO]               : zabbix zabbix-non-supported
* 11-04:28:25 (3372) [INFO] Cleaning up list of fastest mirrors
* 11-04:28:25 (3372) [INFO] Other repos take up 3.7 M of disk space (use --verbose for details)
* 11-04:28:25 (3382) [INFO] 
* 11-04:28:25 (3361) [INFO] Running: /usr/bin/yum check-update
* 11-04:28:25 (3362) [INFO] 
* 11-04:28:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:28:25 (3372) [INFO] Determining fastest mirrors
* 11-04:28:30 (3372) [INFO]  * EA4: 208.100.0.204
* 11-04:28:30 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 11-04:28:30 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 11-04:28:30 (3372) [INFO]  * epel: mirror.dst.ca
* 11-04:28:30 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 11-04:28:53 (3372) [INFO] 
* 11-04:28:53 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 11-04:28:53 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 11-04:28:53 (3382) [INFO] 
* 11-04:28:53 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 11-04:28:53 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 11-04:28:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 11-04:28:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 11-04:28:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-11_04:28:54_modified_for_AlmaLinux_8.json
* 11-04:28:54 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 11-04:28:54 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 12-04:27:02 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 12-04:27:04 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 12-04:27:04 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 12-04:27:04 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 12-04:27:04 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 12-04:27:04 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 12-04:27:19 (2925) [INFO] Checking if your system is up to date: 
* 12-04:27:19 (3361) [INFO] Running: /usr/bin/yum clean all
* 12-04:27:19 (3362) [INFO] 
* 12-04:27:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:27:19 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 12-04:27:19 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 12-04:27:19 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 12-04:27:19 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 12-04:27:19 (3372) [INFO]               : zabbix zabbix-non-supported
* 12-04:27:19 (3372) [INFO] Cleaning up list of fastest mirrors
* 12-04:27:19 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 12-04:27:19 (3382) [INFO] 
* 12-04:27:19 (3361) [INFO] Running: /usr/bin/yum check-update
* 12-04:27:19 (3362) [INFO] 
* 12-04:27:20 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:27:20 (3372) [INFO] Determining fastest mirrors
* 12-04:27:24 (3372) [INFO]  * EA4: 208.100.0.204
* 12-04:27:24 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 12-04:27:24 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 12-04:27:24 (3372) [INFO]  * epel: mirror.dst.ca
* 12-04:27:24 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 12-04:27:48 (3372) [INFO] 
* 12-04:27:48 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 12-04:27:48 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 12-04:27:49 (3382) [INFO] 
* 12-04:27:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 12-04:27:49 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 12-04:27:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 12-04:27:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 12-04:27:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-12_04:27:50_modified_for_AlmaLinux_8.json
* 12-04:27:50 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 12-04:27:50 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 13-04:26:36 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 13-04:26:37 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 13-04:26:37 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 13-04:26:37 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 13-04:26:37 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 13-04:26:37 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 13-04:26:56 (2925) [INFO] Checking if your system is up to date: 
* 13-04:26:56 (3361) [INFO] Running: /usr/bin/yum clean all
* 13-04:26:56 (3362) [INFO] 
* 13-04:26:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:26:56 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 13-04:26:56 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 13-04:26:56 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 13-04:26:56 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 13-04:26:56 (3372) [INFO]               : zabbix zabbix-non-supported
* 13-04:26:57 (3372) [INFO] Cleaning up list of fastest mirrors
* 13-04:26:57 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 13-04:26:57 (3382) [INFO] 
* 13-04:26:57 (3361) [INFO] Running: /usr/bin/yum check-update
* 13-04:26:57 (3362) [INFO] 
* 13-04:26:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:26:57 (3372) [INFO] Determining fastest mirrors
* 13-04:27:04 (3372) [INFO]  * EA4: 208.100.0.204
* 13-04:27:04 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 13-04:27:04 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 13-04:27:04 (3372) [INFO]  * epel: mirror.dst.ca
* 13-04:27:04 (3372) [INFO]  * remi-safe: mirror.team-cymru.com
* 13-04:27:31 (3372) [INFO] 
* 13-04:27:31 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 13-04:27:31 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 13-04:27:31 (3382) [INFO] 
* 13-04:27:31 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 13-04:27:31 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 13-04:27:31 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 13-04:27:31 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 13-04:27:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-13_04:27:32_modified_for_AlmaLinux_8.json
* 13-04:27:32 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 13-04:27:32 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 14-04:26:52 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 14-04:26:54 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 14-04:26:54 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 14-04:26:54 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 14-04:26:54 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 14-04:26:54 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 14-04:27:12 (2925) [INFO] Checking if your system is up to date: 
* 14-04:27:12 (3361) [INFO] Running: /usr/bin/yum clean all
* 14-04:27:12 (3362) [INFO] 
* 14-04:27:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:27:12 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 14-04:27:12 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 14-04:27:12 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 14-04:27:12 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 14-04:27:12 (3372) [INFO]               : zabbix zabbix-non-supported
* 14-04:27:12 (3372) [INFO] Cleaning up list of fastest mirrors
* 14-04:27:12 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 14-04:27:12 (3382) [INFO] 
* 14-04:27:12 (3361) [INFO] Running: /usr/bin/yum check-update
* 14-04:27:12 (3362) [INFO] 
* 14-04:27:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:27:13 (3372) [INFO] Determining fastest mirrors
* 14-04:27:17 (3372) [INFO]  * EA4: 208.100.0.204
* 14-04:27:17 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 14-04:27:17 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 14-04:27:17 (3372) [INFO]  * epel: mirror.dst.ca
* 14-04:27:17 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 14-04:27:40 (3372) [INFO] 
* 14-04:27:40 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 14-04:27:40 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 14-04:27:40 (3382) [INFO] 
* 14-04:27:40 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 14-04:27:40 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 14-04:27:40 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 14-04:27:40 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 14-04:27:42 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-14_04:27:42_modified_for_AlmaLinux_8.json
* 14-04:27:42 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 14-04:27:42 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 15-04:27:37 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 15-04:27:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 15-04:27:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 15-04:27:40 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 15-04:27:40 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 15-04:27:40 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 15-04:27:54 (2925) [INFO] Checking if your system is up to date: 
* 15-04:27:54 (3361) [INFO] Running: /usr/bin/yum clean all
* 15-04:27:54 (3362) [INFO] 
* 15-04:27:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:27:55 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 15-04:27:55 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 15-04:27:55 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 15-04:27:55 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 15-04:27:55 (3372) [INFO]               : zabbix zabbix-non-supported
* 15-04:27:55 (3372) [INFO] Cleaning up list of fastest mirrors
* 15-04:27:55 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 15-04:27:55 (3382) [INFO] 
* 15-04:27:55 (3361) [INFO] Running: /usr/bin/yum check-update
* 15-04:27:55 (3362) [INFO] 
* 15-04:27:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:27:55 (3372) [INFO] Determining fastest mirrors
* 15-04:28:00 (3372) [INFO]  * EA4: 208.100.0.204
* 15-04:28:00 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 15-04:28:00 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 15-04:28:00 (3372) [INFO]  * epel: mirror.dst.ca
* 15-04:28:00 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 15-04:28:22 (3372) [INFO] 
* 15-04:28:22 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 15-04:28:22 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 15-04:28:22 (3382) [INFO] 
* 15-04:28:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 15-04:28:22 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 15-04:28:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 15-04:28:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 15-04:28:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-15_04:28:23_modified_for_AlmaLinux_8.json
* 15-04:28:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 15-04:28:23 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 16-04:27:50 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 16-04:27:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 16-04:27:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 16-04:27:53 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 16-04:27:53 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 16-04:27:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 16-04:28:09 (2925) [INFO] Checking if your system is up to date: 
* 16-04:28:09 (3361) [INFO] Running: /usr/bin/yum clean all
* 16-04:28:09 (3362) [INFO] 
* 16-04:28:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:28:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 16-04:28:09 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 16-04:28:09 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 16-04:28:09 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 16-04:28:09 (3372) [INFO]               : zabbix zabbix-non-supported
* 16-04:28:09 (3372) [INFO] Cleaning up list of fastest mirrors
* 16-04:28:09 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 16-04:28:09 (3382) [INFO] 
* 16-04:28:09 (3361) [INFO] Running: /usr/bin/yum check-update
* 16-04:28:09 (3362) [INFO] 
* 16-04:28:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:28:10 (3372) [INFO] Determining fastest mirrors
* 16-04:28:14 (3372) [INFO]  * EA4: 208.100.0.204
* 16-04:28:14 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 16-04:28:14 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 16-04:28:14 (3372) [INFO]  * epel: mirror.xenyth.net
* 16-04:28:14 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 16-04:28:38 (3372) [INFO] 
* 16-04:28:38 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 16-04:28:38 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 16-04:28:38 (3382) [INFO] 
* 16-04:28:38 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 16-04:28:38 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 16-04:28:38 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 16-04:28:38 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 16-04:28:39 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-16_04:28:39_modified_for_AlmaLinux_8.json
* 16-04:28:39 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 16-04:28:39 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 17-04:26:58 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 17-04:27:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 17-04:27:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 17-04:27:01 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 17-04:27:01 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 17-04:27:01 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 17-04:27:18 (2925) [INFO] Checking if your system is up to date: 
* 17-04:27:18 (3361) [INFO] Running: /usr/bin/yum clean all
* 17-04:27:18 (3362) [INFO] 
* 17-04:27:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:27:19 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 17-04:27:19 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 17-04:27:19 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 17-04:27:19 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 17-04:27:19 (3372) [INFO]               : zabbix zabbix-non-supported
* 17-04:27:19 (3372) [INFO] Cleaning up list of fastest mirrors
* 17-04:27:19 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 17-04:27:19 (3382) [INFO] 
* 17-04:27:19 (3361) [INFO] Running: /usr/bin/yum check-update
* 17-04:27:19 (3362) [INFO] 
* 17-04:27:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:27:20 (3372) [INFO] Determining fastest mirrors
* 17-04:27:24 (3372) [INFO]  * EA4: 208.100.0.204
* 17-04:27:24 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 17-04:27:24 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 17-04:27:24 (3372) [INFO]  * epel: mirror.dst.ca
* 17-04:27:24 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 17-04:27:50 (3372) [INFO] 
* 17-04:27:50 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 17-04:27:50 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 17-04:27:51 (3382) [INFO] 
* 17-04:27:51 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 17-04:27:51 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 17-04:27:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 17-04:27:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 17-04:27:52 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-17_04:27:52_modified_for_AlmaLinux_8.json
* 17-04:27:52 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 17-04:27:52 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 18-04:27:14 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 18-04:27:16 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 18-04:27:16 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 18-04:27:16 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 18-04:27:16 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 18-04:27:16 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 18-04:27:33 (2925) [INFO] Checking if your system is up to date: 
* 18-04:27:33 (3361) [INFO] Running: /usr/bin/yum clean all
* 18-04:27:33 (3362) [INFO] 
* 18-04:27:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:27:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 18-04:27:33 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 18-04:27:33 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 18-04:27:33 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 18-04:27:33 (3372) [INFO]               : zabbix zabbix-non-supported
* 18-04:27:34 (3372) [INFO] Cleaning up list of fastest mirrors
* 18-04:27:34 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 18-04:27:34 (3382) [INFO] 
* 18-04:27:34 (3361) [INFO] Running: /usr/bin/yum check-update
* 18-04:27:34 (3362) [INFO] 
* 18-04:27:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:27:34 (3372) [INFO] Determining fastest mirrors
* 18-04:27:39 (3372) [INFO]  * EA4: 208.100.0.204
* 18-04:27:39 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 18-04:27:39 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 18-04:27:39 (3372) [INFO]  * epel: mirror.dst.ca
* 18-04:27:39 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 18-04:28:04 (3372) [INFO] 
* 18-04:28:04 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 18-04:28:04 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 18-04:28:04 (3382) [INFO] 
* 18-04:28:04 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 18-04:28:04 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 18-04:28:04 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 18-04:28:05 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 18-04:28:05 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-18_04:28:05_modified_for_AlmaLinux_8.json
* 18-04:28:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 18-04:28:06 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 18-04:28:06 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 19-04:26:54 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 19-04:26:56 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 19-04:26:56 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 19-04:26:56 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 19-04:26:56 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 19-04:26:56 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 19-04:27:16 (2925) [INFO] Checking if your system is up to date: 
* 19-04:27:16 (3361) [INFO] Running: /usr/bin/yum clean all
* 19-04:27:16 (3362) [INFO] 
* 19-04:27:16 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:27:17 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 19-04:27:17 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 19-04:27:17 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 19-04:27:17 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 19-04:27:17 (3372) [INFO]               : zabbix zabbix-non-supported
* 19-04:27:17 (3372) [INFO] Cleaning up list of fastest mirrors
* 19-04:27:17 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 19-04:27:17 (3382) [INFO] 
* 19-04:27:17 (3361) [INFO] Running: /usr/bin/yum check-update
* 19-04:27:17 (3362) [INFO] 
* 19-04:27:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:27:17 (3372) [INFO] Determining fastest mirrors
* 19-04:27:22 (3372) [INFO]  * EA4: 208.100.0.204
* 19-04:27:22 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 19-04:27:22 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 19-04:27:22 (3372) [INFO]  * epel: mirror.dst.ca
* 19-04:27:22 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 19-04:27:45 (3372) [INFO] 
* 19-04:27:45 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 19-04:27:45 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 19-04:27:45 (3382) [INFO] 
* 19-04:27:45 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 19-04:27:45 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 19-04:27:45 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 19-04:27:45 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 19-04:27:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-19_04:27:47_modified_for_AlmaLinux_8.json
* 19-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 19-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 19-04:27:47 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 20-04:27:16 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 20-04:27:18 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 20-04:27:18 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 20-04:27:18 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 20-04:27:18 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 20-04:27:18 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 20-04:27:41 (2925) [INFO] Checking if your system is up to date: 
* 20-04:27:41 (3361) [INFO] Running: /usr/bin/yum clean all
* 20-04:27:41 (3362) [INFO] 
* 20-04:27:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:27:41 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 20-04:27:41 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 20-04:27:41 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 20-04:27:41 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 20-04:27:41 (3372) [INFO]               : zabbix zabbix-non-supported
* 20-04:27:41 (3372) [INFO] Cleaning up list of fastest mirrors
* 20-04:27:41 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 20-04:27:41 (3382) [INFO] 
* 20-04:27:41 (3361) [INFO] Running: /usr/bin/yum check-update
* 20-04:27:41 (3362) [INFO] 
* 20-04:27:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:27:42 (3372) [INFO] Determining fastest mirrors
* 20-04:27:49 (3372) [INFO]  * EA4: 208.100.0.204
* 20-04:27:49 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 20-04:27:49 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 20-04:27:49 (3372) [INFO]  * epel: mirror.dst.ca
* 20-04:27:49 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 20-04:28:15 (3372) [INFO] 
* 20-04:28:15 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 20-04:28:15 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 20-04:28:15 (3382) [INFO] 
* 20-04:28:15 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 20-04:28:15 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 20-04:28:15 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 20-04:28:15 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 20-04:28:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-20_04:28:18_modified_for_AlmaLinux_8.json
* 20-04:28:18 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 20-04:28:18 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 20-04:28:18 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 21-04:27:09 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 21-04:27:15 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 21-04:27:15 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 21-04:27:15 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 21-04:27:15 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 21-04:27:15 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 21-04:27:38 (2925) [INFO] Checking if your system is up to date: 
* 21-04:27:38 (3361) [INFO] Running: /usr/bin/yum clean all
* 21-04:27:38 (3362) [INFO] 
* 21-04:27:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:27:39 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 21-04:27:39 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 21-04:27:39 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 21-04:27:39 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 21-04:27:39 (3372) [INFO]               : zabbix zabbix-non-supported
* 21-04:27:39 (3372) [INFO] Cleaning up list of fastest mirrors
* 21-04:27:39 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 21-04:27:39 (3382) [INFO] 
* 21-04:27:39 (3361) [INFO] Running: /usr/bin/yum check-update
* 21-04:27:39 (3362) [INFO] 
* 21-04:27:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:27:40 (3372) [INFO] Determining fastest mirrors
* 21-04:27:44 (3372) [INFO]  * EA4: 63.247.64.58
* 21-04:27:44 (3372) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 21-04:27:44 (3372) [INFO]  * cpanel-plugins: 63.247.64.58
* 21-04:27:44 (3372) [INFO]  * epel: mirror.dst.ca
* 21-04:27:44 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 21-04:28:13 (3372) [INFO] 
* 21-04:28:13 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 21-04:28:13 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 21-04:28:14 (3382) [INFO] 
* 21-04:28:14 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 21-04:28:14 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 21-04:28:14 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 21-04:28:14 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 21-04:28:15 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-21_04:28:15_modified_for_AlmaLinux_8.json
* 21-04:28:15 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 21-04:28:15 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 21-04:28:15 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 22-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 22-04:27:46 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 22-04:27:46 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 22-04:27:46 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 22-04:27:46 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 22-04:27:46 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 22-04:28:33 (2925) [INFO] Checking if your system is up to date: 
* 22-04:28:33 (3361) [INFO] Running: /usr/bin/yum clean all
* 22-04:28:33 (3362) [INFO] 
* 22-04:28:36 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:28:36 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 22-04:28:36 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 22-04:28:36 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 22-04:28:36 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 22-04:28:36 (3372) [INFO]               : zabbix zabbix-non-supported
* 22-04:28:37 (3372) [INFO] Cleaning up list of fastest mirrors
* 22-04:28:37 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 22-04:28:37 (3382) [INFO] 
* 22-04:28:37 (3361) [INFO] Running: /usr/bin/yum check-update
* 22-04:28:37 (3362) [INFO] 
* 22-04:28:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:28:37 (3372) [INFO] Determining fastest mirrors
* 22-04:28:50 (3372) [INFO]  * EA4: 63.247.64.58
* 22-04:28:50 (3372) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 22-04:28:50 (3372) [INFO]  * cpanel-plugins: 63.247.64.58
* 22-04:28:50 (3372) [INFO]  * epel: mirror.dst.ca
* 22-04:28:50 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 22-04:29:22 (3372) [INFO] 
* 22-04:29:22 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 22-04:29:22 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 22-04:29:22 (3382) [INFO] 
* 22-04:29:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 22-04:29:22 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 22-04:29:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 22-04:29:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 22-04:29:24 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-22_04:29:24_modified_for_AlmaLinux_8.json
* 22-04:29:24 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 22-04:29:24 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 22-04:29:24 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 23-04:28:04 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 23-04:28:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 23-04:28:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 23-04:28:06 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 23-04:28:06 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 23-04:28:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 23-04:28:32 (2925) [INFO] Checking if your system is up to date: 
* 23-04:28:32 (3361) [INFO] Running: /usr/bin/yum clean all
* 23-04:28:32 (3362) [INFO] 
* 23-04:28:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:28:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 23-04:28:33 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 23-04:28:33 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 23-04:28:33 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 23-04:28:33 (3372) [INFO]               : zabbix zabbix-non-supported
* 23-04:28:33 (3372) [INFO] Cleaning up list of fastest mirrors
* 23-04:28:33 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 23-04:28:33 (3382) [INFO] 
* 23-04:28:33 (3361) [INFO] Running: /usr/bin/yum check-update
* 23-04:28:33 (3362) [INFO] 
* 23-04:28:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:28:34 (3372) [INFO] Determining fastest mirrors
* 23-04:28:37 (3372) [INFO]  * EA4: 63.247.64.58
* 23-04:28:37 (3372) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 23-04:28:37 (3372) [INFO]  * cpanel-plugins: 63.247.64.58
* 23-04:28:37 (3372) [INFO]  * epel: mirror.dst.ca
* 23-04:28:37 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 23-04:29:12 (3372) [INFO] 
* 23-04:29:12 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 23-04:29:12 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 23-04:29:12 (3382) [INFO] 
* 23-04:29:12 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 23-04:29:12 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 23-04:29:12 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 23-04:29:12 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 23-04:29:13 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-23_04:29:13_modified_for_AlmaLinux_8.json
* 23-04:29:13 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 23-04:29:14 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 23-04:29:14 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 24-04:28:41 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 24-04:28:48 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 24-04:28:48 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 24-04:28:48 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 24-04:28:48 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 24-04:28:48 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 24-04:29:06 (2925) [INFO] Checking if your system is up to date: 
* 24-04:29:06 (3361) [INFO] Running: /usr/bin/yum clean all
* 24-04:29:06 (3362) [INFO] 
* 24-04:29:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:29:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 24-04:29:06 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 24-04:29:06 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 24-04:29:06 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 24-04:29:06 (3372) [INFO]               : zabbix zabbix-non-supported
* 24-04:29:07 (3372) [INFO] Cleaning up list of fastest mirrors
* 24-04:29:07 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 24-04:29:07 (3382) [INFO] 
* 24-04:29:07 (3361) [INFO] Running: /usr/bin/yum check-update
* 24-04:29:07 (3362) [INFO] 
* 24-04:29:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:29:08 (3372) [INFO] Determining fastest mirrors
* 24-04:29:12 (3372) [INFO]  * EA4: 208.100.0.204
* 24-04:29:12 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 24-04:29:13 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 24-04:29:13 (3372) [INFO]  * epel: mirror.xenyth.net
* 24-04:29:13 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 24-04:29:37 (3372) [INFO] 
* 24-04:29:37 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 24-04:29:37 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 24-04:29:37 (3382) [INFO] 
* 24-04:29:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 24-04:29:37 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 24-04:29:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 24-04:29:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 24-04:29:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-24_04:29:38_modified_for_AlmaLinux_8.json
* 24-04:29:38 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 24-04:29:39 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 24-04:29:39 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 25-04:27:05 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 25-04:27:10 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 25-04:27:10 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 25-04:27:10 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 25-04:27:10 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 25-04:27:10 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 25-04:27:31 (2925) [INFO] Checking if your system is up to date: 
* 25-04:27:31 (3361) [INFO] Running: /usr/bin/yum clean all
* 25-04:27:31 (3362) [INFO] 
* 25-04:27:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:27:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 25-04:27:32 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 25-04:27:32 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 25-04:27:32 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 25-04:27:32 (3372) [INFO]               : zabbix zabbix-non-supported
* 25-04:27:32 (3372) [INFO] Cleaning up list of fastest mirrors
* 25-04:27:32 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 25-04:27:32 (3382) [INFO] 
* 25-04:27:32 (3361) [INFO] Running: /usr/bin/yum check-update
* 25-04:27:32 (3362) [INFO] 
* 25-04:27:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:27:33 (3372) [INFO] Determining fastest mirrors
* 25-04:27:37 (3372) [INFO]  * EA4: 208.100.0.204
* 25-04:27:37 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 25-04:27:37 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 25-04:27:37 (3372) [INFO]  * epel: mirror.dst.ca
* 25-04:27:37 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 25-04:28:05 (3372) [INFO] 
* 25-04:28:05 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 25-04:28:05 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 25-04:28:06 (3382) [INFO] 
* 25-04:28:06 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 25-04:28:06 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 25-04:28:06 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 25-04:28:06 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 25-04:28:07 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-25_04:28:07_modified_for_AlmaLinux_8.json
* 25-04:28:07 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 25-04:28:07 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 25-04:28:07 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 26-04:27:42 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 26-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 26-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 26-04:27:47 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 26-04:27:47 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 26-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 26-04:28:06 (2925) [INFO] Checking if your system is up to date: 
* 26-04:28:06 (3361) [INFO] Running: /usr/bin/yum clean all
* 26-04:28:06 (3362) [INFO] 
* 26-04:28:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:28:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 26-04:28:06 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 26-04:28:06 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 26-04:28:06 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 26-04:28:06 (3372) [INFO]               : zabbix zabbix-non-supported
* 26-04:28:07 (3372) [INFO] Cleaning up list of fastest mirrors
* 26-04:28:07 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 26-04:28:07 (3382) [INFO] 
* 26-04:28:07 (3361) [INFO] Running: /usr/bin/yum check-update
* 26-04:28:07 (3362) [INFO] 
* 26-04:28:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:28:07 (3372) [INFO] Determining fastest mirrors
* 26-04:28:11 (3372) [INFO]  * EA4: 208.100.0.204
* 26-04:28:11 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 26-04:28:11 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 26-04:28:11 (3372) [INFO]  * epel: mirror.dst.ca
* 26-04:28:11 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 26-04:28:38 (3372) [INFO] 
* 26-04:28:38 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 26-04:28:38 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 26-04:28:39 (3382) [INFO] 
* 26-04:28:39 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 26-04:28:39 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 26-04:28:39 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 26-04:28:39 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 26-04:28:40 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-26_04:28:40_modified_for_AlmaLinux_8.json
* 26-04:28:40 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 26-04:28:40 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 26-04:28:40 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 27-04:27:40 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 27-04:27:42 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 27-04:27:42 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 27-04:27:42 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 27-04:27:42 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 27-04:27:42 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 27-04:28:04 (2925) [INFO] Checking if your system is up to date: 
* 27-04:28:04 (3361) [INFO] Running: /usr/bin/yum clean all
* 27-04:28:04 (3362) [INFO] 
* 27-04:28:04 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:28:05 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 27-04:28:05 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 27-04:28:05 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 27-04:28:05 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 27-04:28:05 (3372) [INFO]               : zabbix zabbix-non-supported
* 27-04:28:05 (3372) [INFO] Cleaning up list of fastest mirrors
* 27-04:28:05 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 27-04:28:05 (3382) [INFO] 
* 27-04:28:05 (3361) [INFO] Running: /usr/bin/yum check-update
* 27-04:28:05 (3362) [INFO] 
* 27-04:28:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:28:05 (3372) [INFO] Determining fastest mirrors
* 27-04:28:10 (3372) [INFO]  * EA4: 208.100.0.204
* 27-04:28:10 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 27-04:28:10 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 27-04:28:10 (3372) [INFO]  * epel: mirror.dst.ca
* 27-04:28:10 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 27-04:28:36 (3372) [INFO] 
* 27-04:28:36 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 27-04:28:36 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 27-04:28:36 (3382) [INFO] 
* 27-04:28:36 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 27-04:28:36 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 27-04:28:36 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 27-04:28:36 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 27-04:28:37 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-27_04:28:37_modified_for_AlmaLinux_8.json
* 27-04:28:37 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 27-04:28:37 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 27-04:28:37 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 28-04:26:53 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 28-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 28-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 28-04:26:59 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 28-04:26:59 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 28-04:26:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 28-04:27:18 (2925) [INFO] Checking if your system is up to date: 
* 28-04:27:18 (3361) [INFO] Running: /usr/bin/yum clean all
* 28-04:27:18 (3362) [INFO] 
* 28-04:27:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:27:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 28-04:27:18 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 28-04:27:18 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 28-04:27:18 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 28-04:27:18 (3372) [INFO]               : zabbix zabbix-non-supported
* 28-04:27:19 (3372) [INFO] Cleaning up list of fastest mirrors
* 28-04:27:19 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 28-04:27:19 (3382) [INFO] 
* 28-04:27:19 (3361) [INFO] Running: /usr/bin/yum check-update
* 28-04:27:19 (3362) [INFO] 
* 28-04:27:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:27:19 (3372) [INFO] Determining fastest mirrors
* 28-04:27:24 (3372) [INFO]  * EA4: 208.100.0.204
* 28-04:27:24 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 28-04:27:24 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 28-04:27:24 (3372) [INFO]  * epel: mirror.xenyth.net
* 28-04:27:24 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 28-04:27:48 (3372) [INFO] 
* 28-04:27:48 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 28-04:27:48 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 28-04:27:48 (3382) [INFO] 
* 28-04:27:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 28-04:27:48 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 28-04:27:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 28-04:27:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 28-04:27:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-28_04:27:49_modified_for_AlmaLinux_8.json
* 28-04:27:49 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 28-04:27:50 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 28-04:27:50 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 29-04:28:23 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 29-04:28:25 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 29-04:28:25 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 29-04:28:25 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 29-04:28:25 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 29-04:28:25 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 29-04:28:42 (2925) [INFO] Checking if your system is up to date: 
* 29-04:28:42 (3361) [INFO] Running: /usr/bin/yum clean all
* 29-04:28:42 (3362) [INFO] 
* 29-04:28:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 29-04:28:42 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 29-04:28:42 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 29-04:28:42 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 29-04:28:42 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 29-04:28:42 (3372) [INFO]               : zabbix zabbix-non-supported
* 29-04:28:43 (3372) [INFO] Cleaning up list of fastest mirrors
* 29-04:28:43 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 29-04:28:43 (3382) [INFO] 
* 29-04:28:43 (3361) [INFO] Running: /usr/bin/yum check-update
* 29-04:28:43 (3362) [INFO] 
* 29-04:28:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 29-04:28:44 (3372) [INFO] Determining fastest mirrors
* 29-04:28:49 (3372) [INFO]  * EA4: 208.100.0.204
* 29-04:28:49 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 29-04:28:49 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 29-04:28:49 (3372) [INFO]  * epel: mirror.xenyth.net
* 29-04:28:49 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 29-04:29:17 (3372) [INFO] 
* 29-04:29:17 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 29-04:29:17 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 29-04:29:17 (3382) [INFO] 
* 29-04:29:17 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 29-04:29:17 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 29-04:29:17 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 29-04:29:17 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 29-04:29:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-29_04:29:18_modified_for_AlmaLinux_8.json
* 29-04:29:18 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 29-04:29:18 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 29-04:29:18 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 30-04:28:07 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 30-04:28:09 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 30-04:28:09 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 30-04:28:09 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 30-04:28:09 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 30-04:28:09 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 30-04:28:27 (2925) [INFO] Checking if your system is up to date: 
* 30-04:28:27 (3361) [INFO] Running: /usr/bin/yum clean all
* 30-04:28:27 (3362) [INFO] 
* 30-04:28:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 30-04:28:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 30-04:28:28 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 30-04:28:28 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 30-04:28:28 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 30-04:28:28 (3372) [INFO]               : zabbix zabbix-non-supported
* 30-04:28:28 (3372) [INFO] Cleaning up list of fastest mirrors
* 30-04:28:28 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 30-04:28:28 (3382) [INFO] 
* 30-04:28:28 (3361) [INFO] Running: /usr/bin/yum check-update
* 30-04:28:28 (3362) [INFO] 
* 30-04:28:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 30-04:28:29 (3372) [INFO] Determining fastest mirrors
* 30-04:28:33 (3372) [INFO]  * EA4: 63.247.64.58
* 30-04:28:33 (3372) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 30-04:28:33 (3372) [INFO]  * cpanel-plugins: 63.247.64.58
* 30-04:28:33 (3372) [INFO]  * epel: mirror.dst.ca
* 30-04:28:33 (3372) [INFO]  * remi-safe: mirror.team-cymru.com
* 30-04:28:58 (3372) [INFO] 
* 30-04:28:58 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 30-04:28:58 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 30-04:28:58 (3382) [INFO] 
* 30-04:28:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 30-04:28:58 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 30-04:28:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 30-04:28:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 30-04:28:59 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-30_04:28:59_modified_for_AlmaLinux_8.json
* 30-04:28:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 30-04:29:00 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 30-04:29:00 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 31-04:27:14 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 31-04:27:16 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 31-04:27:16 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 31-04:27:16 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 31-04:27:16 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 31-04:27:16 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 31-04:27:42 (2925) [INFO] Checking if your system is up to date: 
* 31-04:27:42 (3361) [INFO] Running: /usr/bin/yum clean all
* 31-04:27:42 (3362) [INFO] 
* 31-04:27:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 31-04:27:42 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 31-04:27:42 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 31-04:27:42 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 31-04:27:42 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 31-04:27:42 (3372) [INFO]               : zabbix zabbix-non-supported
* 31-04:27:43 (3372) [INFO] Cleaning up list of fastest mirrors
* 31-04:27:43 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 31-04:27:43 (3382) [INFO] 
* 31-04:27:43 (3361) [INFO] Running: /usr/bin/yum check-update
* 31-04:27:43 (3362) [INFO] 
* 31-04:27:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 31-04:27:43 (3372) [INFO] Determining fastest mirrors
* 31-04:27:49 (3372) [INFO]  * EA4: 208.100.0.204
* 31-04:27:49 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 31-04:27:49 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 31-04:27:49 (3372) [INFO]  * epel: epel.mirror.constant.com
* 31-04:27:49 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 31-04:28:21 (3372) [INFO] 
* 31-04:28:21 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 31-04:28:21 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 31-04:28:22 (3382) [INFO] 
* 31-04:28:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 31-04:28:22 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 31-04:28:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 31-04:28:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 31-04:28:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-31_04:28:23_modified_for_AlmaLinux_8.json
* 31-04:28:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 31-04:28:23 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 31-04:28:23 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 01-04:26:58 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 01-04:27:00 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 01-04:27:00 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 01-04:27:00 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 01-04:27:00 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 01-04:27:00 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 01-04:27:21 (2925) [INFO] Checking if your system is up to date: 
* 01-04:27:21 (3361) [INFO] Running: /usr/bin/yum clean all
* 01-04:27:21 (3362) [INFO] 
* 01-04:27:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:27:22 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 01-04:27:22 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 01-04:27:22 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 01-04:27:22 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 01-04:27:22 (3372) [INFO]               : zabbix zabbix-non-supported
* 01-04:27:22 (3372) [INFO] Cleaning up list of fastest mirrors
* 01-04:27:22 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 01-04:27:22 (3382) [INFO] 
* 01-04:27:22 (3361) [INFO] Running: /usr/bin/yum check-update
* 01-04:27:22 (3362) [INFO] 
* 01-04:27:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:27:22 (3372) [INFO] Determining fastest mirrors
* 01-04:27:28 (3372) [INFO]  * EA4: 63.247.64.58
* 01-04:27:28 (3372) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 01-04:27:28 (3372) [INFO]  * cpanel-plugins: 63.247.64.58
* 01-04:27:28 (3372) [INFO]  * epel: mirror.xenyth.net
* 01-04:27:28 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 01-04:27:53 (3372) [INFO] 
* 01-04:27:53 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 01-04:27:53 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 01-04:27:53 (3382) [INFO] 
* 01-04:27:53 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 01-04:27:53 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 01-04:27:56 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 01-04:27:57 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 01-04:27:59 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-01_04:27:59_modified_for_AlmaLinux_8.json
* 01-04:27:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 01-04:27:59 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 01-04:27:59 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 02-04:26:53 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 02-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 02-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 02-04:26:59 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 02-04:26:59 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 02-04:26:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 02-04:27:16 (2925) [INFO] Checking if your system is up to date: 
* 02-04:27:16 (3361) [INFO] Running: /usr/bin/yum clean all
* 02-04:27:16 (3362) [INFO] 
* 02-04:27:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:27:17 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 02-04:27:17 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 02-04:27:17 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 02-04:27:17 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 02-04:27:17 (3372) [INFO]               : zabbix zabbix-non-supported
* 02-04:27:18 (3372) [INFO] Cleaning up list of fastest mirrors
* 02-04:27:18 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 02-04:27:18 (3382) [INFO] 
* 02-04:27:18 (3361) [INFO] Running: /usr/bin/yum check-update
* 02-04:27:18 (3362) [INFO] 
* 02-04:27:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:27:19 (3372) [INFO] Determining fastest mirrors
* 02-04:27:23 (3372) [INFO]  * EA4: 208.100.0.204
* 02-04:27:23 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 02-04:27:23 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 02-04:27:23 (3372) [INFO]  * epel: mirror.xenyth.net
* 02-04:27:23 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 02-04:27:46 (3372) [INFO] 
* 02-04:27:46 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 02-04:27:46 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 02-04:27:46 (3382) [INFO] 
* 02-04:27:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 02-04:27:46 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 02-04:27:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 02-04:27:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 02-04:27:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-02_04:27:47_modified_for_AlmaLinux_8.json
* 02-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 02-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 02-04:27:47 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 03-04:28:43 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 03-04:28:44 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 03-04:28:44 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 03-04:28:44 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 03-04:28:44 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 03-04:28:44 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 03-04:29:01 (2925) [INFO] Checking if your system is up to date: 
* 03-04:29:01 (3361) [INFO] Running: /usr/bin/yum clean all
* 03-04:29:01 (3362) [INFO] 
* 03-04:29:01 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:29:01 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 03-04:29:01 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 03-04:29:01 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 03-04:29:01 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 03-04:29:01 (3372) [INFO]               : zabbix zabbix-non-supported
* 03-04:29:01 (3372) [INFO] Cleaning up list of fastest mirrors
* 03-04:29:01 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 03-04:29:01 (3382) [INFO] 
* 03-04:29:01 (3361) [INFO] Running: /usr/bin/yum check-update
* 03-04:29:01 (3362) [INFO] 
* 03-04:29:02 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:29:02 (3372) [INFO] Determining fastest mirrors
* 03-04:29:06 (3372) [INFO]  * EA4: 208.100.0.204
* 03-04:29:06 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 03-04:29:06 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 03-04:29:06 (3372) [INFO]  * epel: mirror.dst.ca
* 03-04:29:06 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 03-04:29:35 (3372) [INFO] 
* 03-04:29:35 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 03-04:29:35 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 03-04:29:35 (3382) [INFO] 
* 03-04:29:35 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 03-04:29:35 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 03-04:29:35 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 03-04:29:35 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 03-04:29:36 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-03_04:29:36_modified_for_AlmaLinux_8.json
* 03-04:29:36 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 03-04:29:36 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 03-04:29:36 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 04-04:26:58 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 04-04:27:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 04-04:27:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 04-04:27:03 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 04-04:27:03 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 04-04:27:03 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 04-04:27:23 (2925) [INFO] Checking if your system is up to date: 
* 04-04:27:23 (3361) [INFO] Running: /usr/bin/yum clean all
* 04-04:27:23 (3362) [INFO] 
* 04-04:27:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:27:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 04-04:27:23 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 04-04:27:23 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 04-04:27:23 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 04-04:27:23 (3372) [INFO]               : zabbix zabbix-non-supported
* 04-04:27:23 (3372) [INFO] Cleaning up list of fastest mirrors
* 04-04:27:23 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 04-04:27:23 (3382) [INFO] 
* 04-04:27:23 (3361) [INFO] Running: /usr/bin/yum check-update
* 04-04:27:23 (3362) [INFO] 
* 04-04:27:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:27:24 (3372) [INFO] Determining fastest mirrors
* 04-04:27:29 (3372) [INFO]  * EA4: 208.100.0.204
* 04-04:27:29 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 04-04:27:29 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 04-04:27:29 (3372) [INFO]  * epel: mirror.xenyth.net
* 04-04:27:29 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 04-04:27:58 (3372) [INFO] 
* 04-04:27:58 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 04-04:27:58 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 04-04:27:58 (3382) [INFO] 
* 04-04:27:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 04-04:27:58 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 04-04:28:00 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 04-04:28:00 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 04-04:28:01 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-04_04:28:01_modified_for_AlmaLinux_8.json
* 04-04:28:01 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 04-04:28:01 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 04-04:28:01 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 05-04:27:37 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 05-04:27:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 05-04:27:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 05-04:27:40 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 05-04:27:40 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 05-04:27:40 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 05-04:27:55 (2925) [INFO] Checking if your system is up to date: 
* 05-04:27:55 (3361) [INFO] Running: /usr/bin/yum clean all
* 05-04:27:55 (3362) [INFO] 
* 05-04:27:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:27:55 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 05-04:27:55 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 05-04:27:55 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 05-04:27:55 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 05-04:27:55 (3372) [INFO]               : zabbix zabbix-non-supported
* 05-04:27:56 (3372) [INFO] Cleaning up list of fastest mirrors
* 05-04:27:56 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 05-04:27:56 (3382) [INFO] 
* 05-04:27:56 (3361) [INFO] Running: /usr/bin/yum check-update
* 05-04:27:56 (3362) [INFO] 
* 05-04:27:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:27:56 (3372) [INFO] Determining fastest mirrors
* 05-04:28:00 (3372) [INFO]  * EA4: 208.100.0.204
* 05-04:28:00 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 05-04:28:00 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 05-04:28:00 (3372) [INFO]  * epel: mirror.xenyth.net
* 05-04:28:00 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 05-04:28:24 (3372) [INFO] 
* 05-04:28:24 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 05-04:28:24 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 05-04:28:24 (3382) [INFO] 
* 05-04:28:24 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 05-04:28:24 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 05-04:28:24 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 05-04:28:24 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 05-04:28:25 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-05_04:28:25_modified_for_AlmaLinux_8.json
* 05-04:28:25 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 05-04:28:25 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 05-04:28:25 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 06-04:28:19 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 06-04:28:21 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 06-04:28:21 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 06-04:28:21 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 06-04:28:21 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 06-04:28:21 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 06-04:28:40 (2925) [INFO] Checking if your system is up to date: 
* 06-04:28:40 (3361) [INFO] Running: /usr/bin/yum clean all
* 06-04:28:40 (3362) [INFO] 
* 06-04:28:40 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:28:40 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 06-04:28:40 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 06-04:28:40 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 06-04:28:40 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 06-04:28:40 (3372) [INFO]               : zabbix zabbix-non-supported
* 06-04:28:40 (3372) [INFO] Cleaning up list of fastest mirrors
* 06-04:28:40 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 06-04:28:41 (3382) [INFO] 
* 06-04:28:41 (3361) [INFO] Running: /usr/bin/yum check-update
* 06-04:28:41 (3362) [INFO] 
* 06-04:28:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:28:41 (3372) [INFO] Determining fastest mirrors
* 06-04:28:45 (3372) [INFO]  * EA4: 208.100.0.204
* 06-04:28:45 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 06-04:28:45 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 06-04:28:45 (3372) [INFO]  * epel: mirror.xenyth.net
* 06-04:28:45 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 06-04:29:11 (3372) [INFO] 
* 06-04:29:11 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 06-04:29:11 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 06-04:29:11 (3382) [INFO] 
* 06-04:29:11 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 06-04:29:11 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 06-04:29:11 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 06-04:29:11 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 06-04:29:12 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-06_04:29:12_modified_for_AlmaLinux_8.json
* 06-04:29:12 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 06-04:29:12 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 06-04:29:12 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 07-04:26:56 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 07-04:26:58 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 07-04:26:58 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 07-04:26:58 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 07-04:26:58 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 07-04:26:58 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 07-04:27:18 (2925) [INFO] Checking if your system is up to date: 
* 07-04:27:18 (3361) [INFO] Running: /usr/bin/yum clean all
* 07-04:27:18 (3362) [INFO] 
* 07-04:27:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:27:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 07-04:27:18 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 07-04:27:18 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 07-04:27:18 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 07-04:27:18 (3372) [INFO]               : zabbix zabbix-non-supported
* 07-04:27:19 (3372) [INFO] Cleaning up list of fastest mirrors
* 07-04:27:19 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 07-04:27:19 (3382) [INFO] 
* 07-04:27:19 (3361) [INFO] Running: /usr/bin/yum check-update
* 07-04:27:19 (3362) [INFO] 
* 07-04:27:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:27:19 (3372) [INFO] Determining fastest mirrors
* 07-04:27:24 (3372) [INFO]  * EA4: 208.100.0.204
* 07-04:27:24 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 07-04:27:24 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 07-04:27:24 (3372) [INFO]  * epel: epel.mirror.constant.com
* 07-04:27:24 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 07-04:27:49 (3372) [INFO] 
* 07-04:27:49 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 07-04:27:49 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 07-04:27:50 (3382) [INFO] 
* 07-04:27:50 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 07-04:27:50 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 07-04:27:50 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 07-04:27:50 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 07-04:27:51 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-07_04:27:51_modified_for_AlmaLinux_8.json
* 07-04:27:51 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 07-04:27:51 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 07-04:27:51 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 08-04:28:56 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 08-04:28:58 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 08-04:28:58 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 08-04:28:58 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 08-04:28:58 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 08-04:28:58 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 08-04:29:16 (2925) [INFO] Checking if your system is up to date: 
* 08-04:29:16 (3361) [INFO] Running: /usr/bin/yum clean all
* 08-04:29:16 (3362) [INFO] 
* 08-04:29:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:29:17 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 08-04:29:17 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 08-04:29:17 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 08-04:29:17 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 08-04:29:17 (3372) [INFO]               : zabbix zabbix-non-supported
* 08-04:29:17 (3372) [INFO] Cleaning up list of fastest mirrors
* 08-04:29:17 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 08-04:29:17 (3382) [INFO] 
* 08-04:29:17 (3361) [INFO] Running: /usr/bin/yum check-update
* 08-04:29:17 (3362) [INFO] 
* 08-04:29:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:29:18 (3372) [INFO] Determining fastest mirrors
* 08-04:29:24 (3372) [INFO]  * EA4: 208.100.0.204
* 08-04:29:24 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 08-04:29:24 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 08-04:29:24 (3372) [INFO]  * epel: mirror.xenyth.net
* 08-04:29:24 (3372) [INFO]  * remi-safe: mirror.team-cymru.com
* 08-04:29:49 (3372) [INFO] 
* 08-04:29:49 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 08-04:29:49 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 08-04:29:49 (3382) [INFO] 
* 08-04:29:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 08-04:29:49 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 08-04:29:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 08-04:29:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 08-04:29:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-08_04:29:50_modified_for_AlmaLinux_8.json
* 08-04:29:50 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 08-04:29:50 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 08-04:29:50 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 09-04:27:26 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 09-04:27:31 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 09-04:27:31 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 09-04:27:31 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 09-04:27:31 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 09-04:27:31 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 09-04:27:48 (2925) [INFO] Checking if your system is up to date: 
* 09-04:27:48 (3361) [INFO] Running: /usr/bin/yum clean all
* 09-04:27:48 (3362) [INFO] 
* 09-04:27:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 09-04:27:49 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 09-04:27:49 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 09-04:27:49 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 09-04:27:49 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 09-04:27:49 (3372) [INFO]               : zabbix zabbix-non-supported
* 09-04:27:49 (3372) [INFO] Cleaning up list of fastest mirrors
* 09-04:27:49 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 09-04:27:49 (3382) [INFO] 
* 09-04:27:49 (3361) [INFO] Running: /usr/bin/yum check-update
* 09-04:27:49 (3362) [INFO] 
* 09-04:27:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 09-04:27:49 (3372) [INFO] Determining fastest mirrors
* 09-04:27:53 (3372) [INFO]  * EA4: 208.100.0.204
* 09-04:27:53 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 09-04:27:53 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 09-04:27:53 (3372) [INFO]  * epel: mirror.xenyth.net
* 09-04:27:53 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 09-04:28:18 (3372) [INFO] 
* 09-04:28:18 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 09-04:28:18 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 09-04:28:18 (3382) [INFO] 
* 09-04:28:18 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 09-04:28:18 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 09-04:28:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 09-04:28:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 09-04:28:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-09_04:28:19_modified_for_AlmaLinux_8.json
* 09-04:28:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 09-04:28:19 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 09-04:28:19 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 10-04:28:54 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 10-04:29:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 10-04:29:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 10-04:29:03 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 10-04:29:03 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 10-04:29:03 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 10-04:29:55 (2925) [INFO] Checking if your system is up to date: 
* 10-04:29:55 (3361) [INFO] Running: /usr/bin/yum clean all
* 10-04:29:55 (3362) [INFO] 
* 10-04:29:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:29:55 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 10-04:29:55 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 10-04:29:55 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 10-04:29:55 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 10-04:29:55 (3372) [INFO]               : zabbix zabbix-non-supported
* 10-04:29:55 (3372) [INFO] Cleaning up list of fastest mirrors
* 10-04:29:55 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 10-04:29:55 (3382) [INFO] 
* 10-04:29:55 (3361) [INFO] Running: /usr/bin/yum check-update
* 10-04:29:55 (3362) [INFO] 
* 10-04:29:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:29:56 (3372) [INFO] Determining fastest mirrors
* 10-04:30:01 (3372) [INFO]  * EA4: 208.100.0.204
* 10-04:30:01 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 10-04:30:01 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 10-04:30:01 (3372) [INFO]  * epel: mirror.xenyth.net
* 10-04:30:01 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 10-04:31:18 (3372) [INFO] 
* 10-04:31:18 (3372) [INFO] kernel.x86_64                     3.10.0-1160.76.1.el7                   updates
* 10-04:31:18 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 10-04:31:18 (3382) [INFO] 
* 10-04:31:18 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 10-04:31:18 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 10-04:31:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 10-04:31:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 10-04:31:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-10_04:31:19_modified_for_AlmaLinux_8.json
* 10-04:31:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 10-04:31:19 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 10-04:31:19 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 11-04:28:31 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 11-04:28:32 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 11-04:28:32 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 11-04:28:32 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 11-04:28:32 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 11-04:28:32 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 11-04:28:53 (2925) [INFO] Checking if your system is up to date: 
* 11-04:28:53 (3361) [INFO] Running: /usr/bin/yum clean all
* 11-04:28:53 (3362) [INFO] 
* 11-04:28:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:28:53 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 11-04:28:53 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 11-04:28:53 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 11-04:28:53 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 11-04:28:53 (3372) [INFO]               : zabbix zabbix-non-supported
* 11-04:28:53 (3372) [INFO] Cleaning up list of fastest mirrors
* 11-04:28:53 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 11-04:28:53 (3382) [INFO] 
* 11-04:28:53 (3361) [INFO] Running: /usr/bin/yum check-update
* 11-04:28:53 (3362) [INFO] 
* 11-04:28:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:28:54 (3372) [INFO] Determining fastest mirrors
* 11-04:28:58 (3372) [INFO]  * EA4: 208.100.0.204
* 11-04:28:58 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 11-04:28:58 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 11-04:28:58 (3372) [INFO]  * epel: epel.mirror.constant.com
* 11-04:28:58 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 11-04:29:24 (3372) [INFO] 
* 11-04:29:24 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 11-04:29:24 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 11-04:29:25 (3382) [INFO] 
* 11-04:29:25 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 11-04:29:25 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 11-04:29:25 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 11-04:29:25 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 11-04:29:26 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-11_04:29:26_modified_for_AlmaLinux_8.json
* 11-04:29:26 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 11-04:29:26 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 11-04:29:26 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 12-04:28:03 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 12-04:28:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 12-04:28:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 12-04:28:06 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 12-04:28:06 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 12-04:28:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 12-04:28:21 (2925) [INFO] Checking if your system is up to date: 
* 12-04:28:21 (3361) [INFO] Running: /usr/bin/yum clean all
* 12-04:28:21 (3362) [INFO] 
* 12-04:28:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:28:21 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 12-04:28:21 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 12-04:28:21 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 12-04:28:21 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 12-04:28:21 (3372) [INFO]               : zabbix zabbix-non-supported
* 12-04:28:22 (3372) [INFO] Cleaning up list of fastest mirrors
* 12-04:28:22 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 12-04:28:22 (3382) [INFO] 
* 12-04:28:22 (3361) [INFO] Running: /usr/bin/yum check-update
* 12-04:28:22 (3362) [INFO] 
* 12-04:28:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:28:23 (3372) [INFO] Determining fastest mirrors
* 12-04:28:29 (3372) [INFO]  * EA4: 208.100.0.204
* 12-04:28:29 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 12-04:28:29 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 12-04:28:29 (3372) [INFO]  * epel: mirror.xenyth.net
* 12-04:28:29 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 12-04:29:00 (3372) [INFO] 
* 12-04:29:00 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 12-04:29:00 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 12-04:29:00 (3382) [INFO] 
* 12-04:29:00 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 12-04:29:00 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 12-04:29:00 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 12-04:29:00 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 12-04:29:02 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-12_04:29:02_modified_for_AlmaLinux_8.json
* 12-04:29:02 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 12-04:29:02 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 12-04:29:02 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 13-04:27:59 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 13-04:28:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 13-04:28:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 13-04:28:01 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 13-04:28:01 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 13-04:28:01 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 13-04:28:16 (2925) [INFO] Checking if your system is up to date: 
* 13-04:28:16 (3361) [INFO] Running: /usr/bin/yum clean all
* 13-04:28:16 (3362) [INFO] 
* 13-04:28:16 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:28:16 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 13-04:28:16 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 13-04:28:16 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 13-04:28:16 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 13-04:28:16 (3372) [INFO]               : zabbix zabbix-non-supported
* 13-04:28:16 (3372) [INFO] Cleaning up list of fastest mirrors
* 13-04:28:16 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 13-04:28:16 (3382) [INFO] 
* 13-04:28:16 (3361) [INFO] Running: /usr/bin/yum check-update
* 13-04:28:16 (3362) [INFO] 
* 13-04:28:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:28:17 (3372) [INFO] Determining fastest mirrors
* 13-04:28:22 (3372) [INFO]  * EA4: 208.100.0.204
* 13-04:28:22 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 13-04:28:22 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 13-04:28:22 (3372) [INFO]  * epel: mirror.xenyth.net
* 13-04:28:22 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 13-04:28:45 (3372) [INFO] 
* 13-04:28:45 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 13-04:28:45 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 13-04:28:45 (3382) [INFO] 
* 13-04:28:45 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 13-04:28:45 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 13-04:28:45 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 13-04:28:45 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 13-04:28:46 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-13_04:28:46_modified_for_AlmaLinux_8.json
* 13-04:28:46 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 13-04:28:46 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 13-04:28:46 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 14-04:26:52 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 14-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 14-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 14-04:26:59 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 14-04:26:59 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 14-04:26:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 14-04:27:18 (2925) [INFO] Checking if your system is up to date: 
* 14-04:27:18 (3361) [INFO] Running: /usr/bin/yum clean all
* 14-04:27:18 (3362) [INFO] 
* 14-04:27:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:27:19 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 14-04:27:19 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 14-04:27:19 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 14-04:27:19 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 14-04:27:19 (3372) [INFO]               : zabbix zabbix-non-supported
* 14-04:27:19 (3372) [INFO] Cleaning up list of fastest mirrors
* 14-04:27:19 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 14-04:27:19 (3382) [INFO] 
* 14-04:27:19 (3361) [INFO] Running: /usr/bin/yum check-update
* 14-04:27:19 (3362) [INFO] 
* 14-04:27:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:27:20 (3372) [INFO] Determining fastest mirrors
* 14-04:27:23 (3372) [INFO]  * EA4: 208.100.0.204
* 14-04:27:23 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 14-04:27:23 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 14-04:27:23 (3372) [INFO]  * epel: mirror.xenyth.net
* 14-04:27:23 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 14-04:27:51 (3372) [INFO] 
* 14-04:27:51 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 14-04:27:51 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 14-04:27:51 (3382) [INFO] 
* 14-04:27:51 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 14-04:27:51 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 14-04:27:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 14-04:27:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 14-04:27:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-14_04:27:53_modified_for_AlmaLinux_8.json
* 14-04:27:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 14-04:27:53 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 14-04:27:53 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 15-04:30:18 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 15-04:30:20 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 15-04:30:20 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 15-04:30:20 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 15-04:30:20 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 15-04:30:20 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 15-04:30:36 (2925) [INFO] Checking if your system is up to date: 
* 15-04:30:36 (3361) [INFO] Running: /usr/bin/yum clean all
* 15-04:30:36 (3362) [INFO] 
* 15-04:30:36 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:30:37 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 15-04:30:37 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 15-04:30:37 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 15-04:30:37 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 15-04:30:37 (3372) [INFO]               : zabbix zabbix-non-supported
* 15-04:30:37 (3372) [INFO] Cleaning up list of fastest mirrors
* 15-04:30:37 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 15-04:30:37 (3382) [INFO] 
* 15-04:30:37 (3361) [INFO] Running: /usr/bin/yum check-update
* 15-04:30:37 (3362) [INFO] 
* 15-04:30:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:30:37 (3372) [INFO] Determining fastest mirrors
* 15-04:30:42 (3372) [INFO]  * EA4: 208.100.0.204
* 15-04:30:42 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 15-04:30:42 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 15-04:30:42 (3372) [INFO]  * epel: mirror.dst.ca
* 15-04:30:42 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 15-04:31:08 (3372) [INFO] 
* 15-04:31:08 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 15-04:31:08 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 15-04:31:08 (3382) [INFO] 
* 15-04:31:08 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 15-04:31:08 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 15-04:31:08 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 15-04:31:08 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 15-04:31:10 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-15_04:31:10_modified_for_AlmaLinux_8.json
* 15-04:31:10 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 15-04:31:10 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 15-04:31:10 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 16-04:27:08 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 16-04:27:10 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 16-04:27:10 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 16-04:27:10 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 16-04:27:10 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 16-04:27:10 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 16-04:27:27 (2925) [INFO] Checking if your system is up to date: 
* 16-04:27:27 (3361) [INFO] Running: /usr/bin/yum clean all
* 16-04:27:27 (3362) [INFO] 
* 16-04:27:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:27:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 16-04:27:28 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 16-04:27:28 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 16-04:27:28 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 16-04:27:28 (3372) [INFO]               : zabbix zabbix-non-supported
* 16-04:27:28 (3372) [INFO] Cleaning up list of fastest mirrors
* 16-04:27:28 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 16-04:27:28 (3382) [INFO] 
* 16-04:27:28 (3361) [INFO] Running: /usr/bin/yum check-update
* 16-04:27:28 (3362) [INFO] 
* 16-04:27:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:27:29 (3372) [INFO] Determining fastest mirrors
* 16-04:27:32 (3372) [INFO]  * EA4: 208.100.0.204
* 16-04:27:32 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 16-04:27:32 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 16-04:27:32 (3372) [INFO]  * epel: mirror.xenyth.net
* 16-04:27:32 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 16-04:27:57 (3372) [INFO] 
* 16-04:27:57 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 16-04:27:57 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 16-04:27:57 (3382) [INFO] 
* 16-04:27:57 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 16-04:27:57 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 16-04:27:57 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 16-04:27:57 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 16-04:27:58 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-16_04:27:58_modified_for_AlmaLinux_8.json
* 16-04:27:58 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 16-04:27:58 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 16-04:27:58 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 17-04:27:30 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 17-04:27:31 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 17-04:27:31 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 17-04:27:31 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 17-04:27:31 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 17-04:27:31 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 17-04:27:50 (2925) [INFO] Checking if your system is up to date: 
* 17-04:27:50 (3361) [INFO] Running: /usr/bin/yum clean all
* 17-04:27:50 (3362) [INFO] 
* 17-04:27:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:27:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 17-04:27:51 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 17-04:27:51 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 17-04:27:51 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 17-04:27:51 (3372) [INFO]               : zabbix zabbix-non-supported
* 17-04:27:51 (3372) [INFO] Cleaning up list of fastest mirrors
* 17-04:27:51 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 17-04:27:51 (3382) [INFO] 
* 17-04:27:51 (3361) [INFO] Running: /usr/bin/yum check-update
* 17-04:27:51 (3362) [INFO] 
* 17-04:27:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:27:51 (3372) [INFO] Determining fastest mirrors
* 17-04:27:57 (3372) [INFO]  * EA4: 208.100.0.204
* 17-04:27:57 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 17-04:27:57 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 17-04:27:57 (3372) [INFO]  * epel: mirror.xenyth.net
* 17-04:27:57 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 17-04:28:19 (3372) [INFO] 
* 17-04:28:19 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 17-04:28:19 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 17-04:28:19 (3382) [INFO] 
* 17-04:28:19 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 17-04:28:19 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 17-04:28:19 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 17-04:28:19 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 17-04:28:20 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-17_04:28:20_modified_for_AlmaLinux_8.json
* 17-04:28:20 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 17-04:28:20 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 17-04:28:20 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 18-04:27:41 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 18-04:27:44 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 18-04:27:44 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 18-04:27:44 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 18-04:27:44 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 18-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 18-04:28:07 (2925) [INFO] Checking if your system is up to date: 
* 18-04:28:07 (3361) [INFO] Running: /usr/bin/yum clean all
* 18-04:28:07 (3362) [INFO] 
* 18-04:28:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:28:07 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 18-04:28:07 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 18-04:28:07 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 18-04:28:07 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 18-04:28:07 (3372) [INFO]               : zabbix zabbix-non-supported
* 18-04:28:08 (3372) [INFO] Cleaning up list of fastest mirrors
* 18-04:28:08 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 18-04:28:08 (3382) [INFO] 
* 18-04:28:08 (3361) [INFO] Running: /usr/bin/yum check-update
* 18-04:28:08 (3362) [INFO] 
* 18-04:28:08 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:28:08 (3372) [INFO] Determining fastest mirrors
* 18-04:28:13 (3372) [INFO]  * EA4: 208.100.0.204
* 18-04:28:13 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 18-04:28:13 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 18-04:28:13 (3372) [INFO]  * epel: mirror.dst.ca
* 18-04:28:13 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 18-04:28:41 (3372) [INFO] 
* 18-04:28:41 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 18-04:28:41 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 18-04:28:41 (3382) [INFO] 
* 18-04:28:41 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 18-04:28:41 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 18-04:28:41 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 18-04:28:41 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 18-04:28:42 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-18_04:28:42_modified_for_AlmaLinux_8.json
* 18-04:28:42 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 18-04:28:43 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 18-04:28:43 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 19-04:29:39 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 19-04:29:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 19-04:29:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 19-04:29:47 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 19-04:29:47 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 19-04:29:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 19-04:30:10 (2925) [INFO] Checking if your system is up to date: 
* 19-04:30:10 (3361) [INFO] Running: /usr/bin/yum clean all
* 19-04:30:10 (3362) [INFO] 
* 19-04:30:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:30:11 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 19-04:30:11 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 19-04:30:11 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 19-04:30:11 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 19-04:30:11 (3372) [INFO]               : zabbix zabbix-non-supported
* 19-04:30:11 (3372) [INFO] Cleaning up list of fastest mirrors
* 19-04:30:11 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 19-04:30:11 (3382) [INFO] 
* 19-04:30:11 (3361) [INFO] Running: /usr/bin/yum check-update
* 19-04:30:11 (3362) [INFO] 
* 19-04:30:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:30:12 (3372) [INFO] Determining fastest mirrors
* 19-04:30:16 (3372) [INFO]  * EA4: 208.100.0.204
* 19-04:30:16 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 19-04:30:16 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 19-04:30:16 (3372) [INFO]  * epel: mirror.dst.ca
* 19-04:30:16 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 19-04:30:42 (3372) [INFO] 
* 19-04:30:42 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 19-04:30:42 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 19-04:30:42 (3382) [INFO] 
* 19-04:30:42 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 19-04:30:42 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 19-04:30:42 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 19-04:30:42 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 19-04:30:43 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-19_04:30:43_modified_for_AlmaLinux_8.json
* 19-04:30:43 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 19-04:30:44 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 19-04:30:44 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 20-04:27:24 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 20-04:27:26 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 20-04:27:26 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 20-04:27:26 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 20-04:27:26 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 20-04:27:26 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 20-04:27:42 (2925) [INFO] Checking if your system is up to date: 
* 20-04:27:42 (3361) [INFO] Running: /usr/bin/yum clean all
* 20-04:27:42 (3362) [INFO] 
* 20-04:27:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:27:42 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 20-04:27:42 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 20-04:27:42 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 20-04:27:42 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 20-04:27:42 (3372) [INFO]               : zabbix zabbix-non-supported
* 20-04:27:42 (3372) [INFO] Cleaning up list of fastest mirrors
* 20-04:27:42 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 20-04:27:43 (3382) [INFO] 
* 20-04:27:43 (3361) [INFO] Running: /usr/bin/yum check-update
* 20-04:27:43 (3362) [INFO] 
* 20-04:27:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:27:43 (3372) [INFO] Determining fastest mirrors
* 20-04:27:48 (3372) [INFO]  * EA4: 208.100.0.204
* 20-04:27:48 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 20-04:27:48 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 20-04:27:48 (3372) [INFO]  * epel: mirror.xenyth.net
* 20-04:27:48 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 20-04:28:12 (3372) [INFO] 
* 20-04:28:12 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 20-04:28:12 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 20-04:28:12 (3382) [INFO] 
* 20-04:28:12 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 20-04:28:12 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 20-04:28:12 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 20-04:28:12 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 20-04:28:14 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-20_04:28:14_modified_for_AlmaLinux_8.json
* 20-04:28:14 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 20-04:28:14 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 20-04:28:14 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 21-04:26:51 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 21-04:26:56 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 21-04:26:56 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 21-04:26:56 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 21-04:26:56 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 21-04:26:56 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 21-04:27:10 (2925) [INFO] Checking if your system is up to date: 
* 21-04:27:10 (3361) [INFO] Running: /usr/bin/yum clean all
* 21-04:27:10 (3362) [INFO] 
* 21-04:27:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:27:11 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 21-04:27:11 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 21-04:27:11 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 21-04:27:11 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 21-04:27:11 (3372) [INFO]               : zabbix zabbix-non-supported
* 21-04:27:11 (3372) [INFO] Cleaning up list of fastest mirrors
* 21-04:27:11 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 21-04:27:11 (3382) [INFO] 
* 21-04:27:11 (3361) [INFO] Running: /usr/bin/yum check-update
* 21-04:27:11 (3362) [INFO] 
* 21-04:27:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:27:11 (3372) [INFO] Determining fastest mirrors
* 21-04:27:16 (3372) [INFO]  * EA4: 208.100.0.204
* 21-04:27:16 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 21-04:27:16 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 21-04:27:16 (3372) [INFO]  * epel: mirror.dst.ca
* 21-04:27:16 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 21-04:27:40 (3372) [INFO] 
* 21-04:27:40 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 21-04:27:40 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 21-04:27:40 (3382) [INFO] 
* 21-04:27:40 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 21-04:27:40 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 21-04:27:40 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 21-04:27:40 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 21-04:27:44 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-21_04:27:43_modified_for_AlmaLinux_8.json
* 21-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 21-04:27:45 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 21-04:27:45 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 22-04:28:16 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 22-04:28:17 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 22-04:28:17 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 22-04:28:17 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 22-04:28:17 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 22-04:28:17 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 22-04:28:46 (2925) [INFO] Checking if your system is up to date: 
* 22-04:28:46 (3361) [INFO] Running: /usr/bin/yum clean all
* 22-04:28:46 (3362) [INFO] 
* 22-04:28:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:28:47 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 22-04:28:47 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 22-04:28:47 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 22-04:28:47 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 22-04:28:47 (3372) [INFO]               : zabbix zabbix-non-supported
* 22-04:28:47 (3372) [INFO] Cleaning up list of fastest mirrors
* 22-04:28:47 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 22-04:28:47 (3382) [INFO] 
* 22-04:28:47 (3361) [INFO] Running: /usr/bin/yum check-update
* 22-04:28:47 (3362) [INFO] 
* 22-04:28:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:28:48 (3372) [INFO] Determining fastest mirrors
* 22-04:28:52 (3372) [INFO]  * EA4: 208.100.0.204
* 22-04:28:52 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 22-04:28:52 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 22-04:28:52 (3372) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 22-04:28:52 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 22-04:29:15 (3372) [INFO] 
* 22-04:29:15 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 22-04:29:15 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 22-04:29:15 (3382) [INFO] 
* 22-04:29:15 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 22-04:29:15 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 22-04:29:15 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 22-04:29:15 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 22-04:29:16 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-22_04:29:16_modified_for_AlmaLinux_8.json
* 22-04:29:16 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 22-04:29:16 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 22-04:29:16 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 23-04:27:12 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 23-04:27:17 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 23-04:27:17 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 23-04:27:17 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 23-04:27:17 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 23-04:27:17 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 23-04:27:34 (2925) [INFO] Checking if your system is up to date: 
* 23-04:27:34 (3361) [INFO] Running: /usr/bin/yum clean all
* 23-04:27:34 (3362) [INFO] 
* 23-04:27:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:27:35 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 23-04:27:35 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 23-04:27:35 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 23-04:27:35 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 23-04:27:35 (3372) [INFO]               : zabbix zabbix-non-supported
* 23-04:27:35 (3372) [INFO] Cleaning up list of fastest mirrors
* 23-04:27:35 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 23-04:27:35 (3382) [INFO] 
* 23-04:27:35 (3361) [INFO] Running: /usr/bin/yum check-update
* 23-04:27:35 (3362) [INFO] 
* 23-04:27:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:27:35 (3372) [INFO] Determining fastest mirrors
* 23-04:27:40 (3372) [INFO]  * EA4: 208.100.0.204
* 23-04:27:40 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 23-04:27:40 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 23-04:27:40 (3372) [INFO]  * epel: mirror.xenyth.net
* 23-04:27:40 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 23-04:28:02 (3372) [INFO] 
* 23-04:28:02 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 23-04:28:02 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 23-04:28:02 (3382) [INFO] 
* 23-04:28:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 23-04:28:02 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 23-04:28:02 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 23-04:28:02 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 23-04:28:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-23_04:28:03_modified_for_AlmaLinux_8.json
* 23-04:28:03 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 23-04:28:04 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 23-04:28:04 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 24-04:26:49 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 24-04:26:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 24-04:26:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 24-04:26:53 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 24-04:26:53 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 24-04:26:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 24-04:27:20 (2925) [INFO] Checking if your system is up to date: 
* 24-04:27:20 (3361) [INFO] Running: /usr/bin/yum clean all
* 24-04:27:20 (3362) [INFO] 
* 24-04:27:20 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:27:20 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 24-04:27:20 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 24-04:27:20 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 24-04:27:20 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 24-04:27:20 (3372) [INFO]               : zabbix zabbix-non-supported
* 24-04:27:20 (3372) [INFO] Cleaning up list of fastest mirrors
* 24-04:27:20 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 24-04:27:20 (3382) [INFO] 
* 24-04:27:20 (3361) [INFO] Running: /usr/bin/yum check-update
* 24-04:27:20 (3362) [INFO] 
* 24-04:27:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:27:21 (3372) [INFO] Determining fastest mirrors
* 24-04:27:26 (3372) [INFO]  * EA4: 208.100.0.204
* 24-04:27:26 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 24-04:27:26 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 24-04:27:26 (3372) [INFO]  * epel: na.edge.kernel.org
* 24-04:27:26 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 24-04:27:48 (3372) [INFO] 
* 24-04:27:48 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 24-04:27:48 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 24-04:27:48 (3382) [INFO] 
* 24-04:27:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 24-04:27:48 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 24-04:27:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 24-04:27:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 24-04:27:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-24_04:27:49_modified_for_AlmaLinux_8.json
* 24-04:27:49 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 24-04:27:50 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 24-04:27:50 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 25-04:26:57 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 25-04:27:00 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 25-04:27:00 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 25-04:27:00 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 25-04:27:00 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 25-04:27:00 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 25-04:27:24 (2925) [INFO] Checking if your system is up to date: 
* 25-04:27:24 (3361) [INFO] Running: /usr/bin/yum clean all
* 25-04:27:24 (3362) [INFO] 
* 25-04:27:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:27:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 25-04:27:25 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 25-04:27:25 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 25-04:27:25 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 25-04:27:25 (3372) [INFO]               : zabbix zabbix-non-supported
* 25-04:27:25 (3372) [INFO] Cleaning up list of fastest mirrors
* 25-04:27:25 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 25-04:27:25 (3382) [INFO] 
* 25-04:27:25 (3361) [INFO] Running: /usr/bin/yum check-update
* 25-04:27:25 (3362) [INFO] 
* 25-04:27:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:27:25 (3372) [INFO] Determining fastest mirrors
* 25-04:27:30 (3372) [INFO]  * EA4: 208.100.0.204
* 25-04:27:30 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 25-04:27:30 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 25-04:27:30 (3372) [INFO]  * epel: mirror.dst.ca
* 25-04:27:30 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 25-04:27:53 (3372) [INFO] 
* 25-04:27:53 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 25-04:27:53 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 25-04:27:54 (3382) [INFO] 
* 25-04:27:54 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 25-04:27:54 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 25-04:27:54 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 25-04:27:54 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 25-04:27:55 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-25_04:27:55_modified_for_AlmaLinux_8.json
* 25-04:27:55 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 25-04:27:55 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 25-04:27:55 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 26-04:28:33 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 26-04:28:35 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 26-04:28:35 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 26-04:28:35 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 26-04:28:35 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 26-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 26-04:28:51 (2925) [INFO] Checking if your system is up to date: 
* 26-04:28:51 (3361) [INFO] Running: /usr/bin/yum clean all
* 26-04:28:51 (3362) [INFO] 
* 26-04:28:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:28:54 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 26-04:28:54 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 26-04:28:54 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 26-04:28:54 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 26-04:28:54 (3372) [INFO]               : zabbix zabbix-non-supported
* 26-04:28:54 (3372) [INFO] Cleaning up list of fastest mirrors
* 26-04:28:54 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 26-04:28:54 (3382) [INFO] 
* 26-04:28:54 (3361) [INFO] Running: /usr/bin/yum check-update
* 26-04:28:54 (3362) [INFO] 
* 26-04:28:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:28:55 (3372) [INFO] Determining fastest mirrors
* 26-04:29:00 (3372) [INFO]  * EA4: 208.100.0.204
* 26-04:29:00 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 26-04:29:00 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 26-04:29:00 (3372) [INFO]  * epel: mirror.dst.ca
* 26-04:29:00 (3372) [INFO]  * remi-safe: mirror.team-cymru.com
* 26-04:29:22 (3372) [INFO] 
* 26-04:29:22 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 26-04:29:22 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 26-04:29:22 (3382) [INFO] 
* 26-04:29:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 26-04:29:22 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 26-04:29:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 26-04:29:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 26-04:29:24 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-26_04:29:24_modified_for_AlmaLinux_8.json
* 26-04:29:24 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 26-04:29:24 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 26-04:29:24 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 27-04:30:02 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 27-04:30:09 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 27-04:30:09 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 27-04:30:09 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 27-04:30:09 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 27-04:30:09 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 27-04:30:33 (2925) [INFO] Checking if your system is up to date: 
* 27-04:30:33 (3361) [INFO] Running: /usr/bin/yum clean all
* 27-04:30:33 (3362) [INFO] 
* 27-04:30:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:30:34 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 27-04:30:34 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 27-04:30:34 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 27-04:30:34 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 27-04:30:34 (3372) [INFO]               : zabbix zabbix-non-supported
* 27-04:30:34 (3372) [INFO] Cleaning up list of fastest mirrors
* 27-04:30:34 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 27-04:30:34 (3382) [INFO] 
* 27-04:30:34 (3361) [INFO] Running: /usr/bin/yum check-update
* 27-04:30:34 (3362) [INFO] 
* 27-04:30:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:30:35 (3372) [INFO] Determining fastest mirrors
* 27-04:30:40 (3372) [INFO]  * EA4: 208.100.0.204
* 27-04:30:40 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 27-04:30:40 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 27-04:30:40 (3372) [INFO]  * epel: mirror.dst.ca
* 27-04:30:40 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 27-04:31:02 (3372) [INFO] 
* 27-04:31:02 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 27-04:31:02 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 27-04:31:02 (3382) [INFO] 
* 27-04:31:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 27-04:31:02 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 27-04:31:02 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 27-04:31:02 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 27-04:31:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-27_04:31:03_modified_for_AlmaLinux_8.json
* 27-04:31:03 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 27-04:31:03 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 27-04:31:03 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 28-04:26:32 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 28-04:26:35 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 28-04:26:35 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 28-04:26:35 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 28-04:26:35 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 28-04:26:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 28-04:26:50 (2925) [INFO] Checking if your system is up to date: 
* 28-04:26:50 (3361) [INFO] Running: /usr/bin/yum clean all
* 28-04:26:50 (3362) [INFO] 
* 28-04:26:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:26:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 28-04:26:51 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 28-04:26:51 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 28-04:26:51 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 28-04:26:51 (3372) [INFO]               : zabbix zabbix-non-supported
* 28-04:26:51 (3372) [INFO] Cleaning up list of fastest mirrors
* 28-04:26:51 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 28-04:26:51 (3382) [INFO] 
* 28-04:26:51 (3361) [INFO] Running: /usr/bin/yum check-update
* 28-04:26:51 (3362) [INFO] 
* 28-04:26:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:26:52 (3372) [INFO] Determining fastest mirrors
* 28-04:26:57 (3372) [INFO]  * EA4: 208.100.0.204
* 28-04:26:57 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 28-04:26:57 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 28-04:26:57 (3372) [INFO]  * epel: mirror.dst.ca
* 28-04:26:57 (3372) [INFO]  * remi-safe: mirror.team-cymru.com
* 28-04:27:20 (3372) [INFO] 
* 28-04:27:20 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 28-04:27:20 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 28-04:27:20 (3382) [INFO] 
* 28-04:27:20 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 28-04:27:20 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 28-04:27:20 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 28-04:27:20 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 28-04:27:21 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-28_04:27:21_modified_for_AlmaLinux_8.json
* 28-04:27:21 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 28-04:27:21 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 28-04:27:21 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 29-04:28:02 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 29-04:28:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 29-04:28:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 29-04:28:03 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 29-04:28:03 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 29-04:28:03 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 29-04:28:23 (2925) [INFO] Checking if your system is up to date: 
* 29-04:28:23 (3361) [INFO] Running: /usr/bin/yum clean all
* 29-04:28:23 (3362) [INFO] 
* 29-04:28:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 29-04:28:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 29-04:28:23 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 29-04:28:23 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 29-04:28:23 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 29-04:28:23 (3372) [INFO]               : zabbix zabbix-non-supported
* 29-04:28:23 (3372) [INFO] Cleaning up list of fastest mirrors
* 29-04:28:23 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 29-04:28:23 (3382) [INFO] 
* 29-04:28:23 (3361) [INFO] Running: /usr/bin/yum check-update
* 29-04:28:23 (3362) [INFO] 
* 29-04:28:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 29-04:28:24 (3372) [INFO] Determining fastest mirrors
* 29-04:28:28 (3372) [INFO]  * EA4: 208.100.0.204
* 29-04:28:28 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 29-04:28:28 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 29-04:28:28 (3372) [INFO]  * epel: mirror.dst.ca
* 29-04:28:28 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 29-04:28:49 (3372) [INFO] 
* 29-04:28:49 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 29-04:28:49 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 29-04:28:50 (3382) [INFO] 
* 29-04:28:50 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 29-04:28:50 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 29-04:28:50 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 29-04:28:50 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 29-04:28:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-29_04:28:53_modified_for_AlmaLinux_8.json
* 29-04:28:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 29-04:28:53 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 29-04:28:53 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 30-04:26:47 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 30-04:26:50 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 30-04:26:50 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 30-04:26:50 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 30-04:26:50 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 30-04:26:50 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 30-04:27:07 (2925) [INFO] Checking if your system is up to date: 
* 30-04:27:07 (3361) [INFO] Running: /usr/bin/yum clean all
* 30-04:27:07 (3362) [INFO] 
* 30-04:27:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 30-04:27:08 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 30-04:27:08 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 30-04:27:08 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 30-04:27:08 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 30-04:27:08 (3372) [INFO]               : zabbix zabbix-non-supported
* 30-04:27:08 (3372) [INFO] Cleaning up list of fastest mirrors
* 30-04:27:08 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 30-04:27:08 (3382) [INFO] 
* 30-04:27:08 (3361) [INFO] Running: /usr/bin/yum check-update
* 30-04:27:08 (3362) [INFO] 
* 30-04:27:08 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 30-04:27:08 (3372) [INFO] Determining fastest mirrors
* 30-04:27:13 (3372) [INFO]  * EA4: 208.100.0.204
* 30-04:27:13 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 30-04:27:13 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 30-04:27:13 (3372) [INFO]  * epel: mirror.dst.ca
* 30-04:27:13 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 30-04:27:36 (3372) [INFO] 
* 30-04:27:36 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 30-04:27:36 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 30-04:27:37 (3382) [INFO] 
* 30-04:27:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 30-04:27:37 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 30-04:27:38 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 30-04:27:38 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 30-04:27:39 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-30_04:27:39_modified_for_AlmaLinux_8.json
* 30-04:27:39 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 30-04:27:39 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 30-04:27:39 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 01-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 01-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 01-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 01-04:27:47 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 01-04:27:47 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 01-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 01-04:28:08 (2925) [INFO] Checking if your system is up to date: 
* 01-04:28:08 (3361) [INFO] Running: /usr/bin/yum clean all
* 01-04:28:08 (3362) [INFO] 
* 01-04:28:08 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:28:08 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 01-04:28:08 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 01-04:28:08 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 01-04:28:08 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 01-04:28:08 (3372) [INFO]               : zabbix zabbix-non-supported
* 01-04:28:08 (3372) [INFO] Cleaning up list of fastest mirrors
* 01-04:28:08 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 01-04:28:08 (3382) [INFO] 
* 01-04:28:08 (3361) [INFO] Running: /usr/bin/yum check-update
* 01-04:28:08 (3362) [INFO] 
* 01-04:28:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:28:09 (3372) [INFO] Determining fastest mirrors
* 01-04:28:13 (3372) [INFO]  * EA4: 208.100.0.204
* 01-04:28:13 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 01-04:28:13 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 01-04:28:13 (3372) [INFO]  * epel: mirror.dst.ca
* 01-04:28:13 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 01-04:28:34 (3372) [INFO] 
* 01-04:28:34 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 01-04:28:34 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 01-04:28:34 (3382) [INFO] 
* 01-04:28:34 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 01-04:28:34 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 01-04:28:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 01-04:28:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 01-04:28:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-01_04:28:35_modified_for_AlmaLinux_8.json
* 01-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 01-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 01-04:28:35 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 02-04:26:48 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 02-04:26:50 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 02-04:26:50 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 02-04:26:50 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 02-04:26:50 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 02-04:26:50 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 02-04:27:06 (2925) [INFO] Checking if your system is up to date: 
* 02-04:27:06 (3361) [INFO] Running: /usr/bin/yum clean all
* 02-04:27:06 (3362) [INFO] 
* 02-04:27:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:27:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 02-04:27:06 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 02-04:27:06 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 02-04:27:06 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 02-04:27:06 (3372) [INFO]               : zabbix zabbix-non-supported
* 02-04:27:06 (3372) [INFO] Cleaning up list of fastest mirrors
* 02-04:27:06 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 02-04:27:06 (3382) [INFO] 
* 02-04:27:06 (3361) [INFO] Running: /usr/bin/yum check-update
* 02-04:27:06 (3362) [INFO] 
* 02-04:27:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:27:07 (3372) [INFO] Determining fastest mirrors
* 02-04:27:11 (3372) [INFO]  * EA4: 208.100.0.204
* 02-04:27:11 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 02-04:27:11 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 02-04:27:11 (3372) [INFO]  * epel: mirror.dst.ca
* 02-04:27:11 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 02-04:27:33 (3372) [INFO] 
* 02-04:27:33 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 02-04:27:33 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 02-04:27:33 (3382) [INFO] 
* 02-04:27:33 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 02-04:27:33 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 02-04:27:33 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 02-04:27:33 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 02-04:27:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-02_04:27:35_modified_for_AlmaLinux_8.json
* 02-04:27:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 02-04:27:35 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 02-04:27:35 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 03-04:28:26 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 03-04:28:28 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 03-04:28:28 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 03-04:28:28 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 03-04:28:28 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 03-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 03-04:28:44 (2925) [INFO] Checking if your system is up to date: 
* 03-04:28:44 (3361) [INFO] Running: /usr/bin/yum clean all
* 03-04:28:44 (3362) [INFO] 
* 03-04:28:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:28:44 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 03-04:28:44 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 03-04:28:44 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 03-04:28:44 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 03-04:28:44 (3372) [INFO]               : zabbix zabbix-non-supported
* 03-04:28:45 (3372) [INFO] Cleaning up list of fastest mirrors
* 03-04:28:45 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 03-04:28:45 (3382) [INFO] 
* 03-04:28:45 (3361) [INFO] Running: /usr/bin/yum check-update
* 03-04:28:45 (3362) [INFO] 
* 03-04:28:45 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:28:46 (3372) [INFO] Determining fastest mirrors
* 03-04:28:51 (3372) [INFO]  * EA4: 208.100.0.204
* 03-04:28:51 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 03-04:28:51 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 03-04:28:51 (3372) [INFO]  * epel: mirror.dst.ca
* 03-04:28:51 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 03-04:29:17 (3372) [INFO] 
* 03-04:29:17 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 03-04:29:17 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 03-04:29:17 (3382) [INFO] 
* 03-04:29:17 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 03-04:29:17 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 03-04:29:17 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 03-04:29:17 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 03-04:29:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-03_04:29:19_modified_for_AlmaLinux_8.json
* 03-04:29:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 03-04:29:19 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 03-04:29:19 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 04-04:28:31 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 04-04:28:35 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 04-04:28:35 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 04-04:28:35 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 04-04:28:35 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 04-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 04-04:28:57 (2925) [INFO] Checking if your system is up to date: 
* 04-04:28:57 (3361) [INFO] Running: /usr/bin/yum clean all
* 04-04:28:57 (3362) [INFO] 
* 04-04:28:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:28:58 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 04-04:28:58 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 04-04:28:58 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 04-04:28:58 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 04-04:28:58 (3372) [INFO]               : zabbix zabbix-non-supported
* 04-04:28:58 (3372) [INFO] Cleaning up list of fastest mirrors
* 04-04:28:58 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 04-04:28:58 (3382) [INFO] 
* 04-04:28:58 (3361) [INFO] Running: /usr/bin/yum check-update
* 04-04:28:58 (3362) [INFO] 
* 04-04:28:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:28:59 (3372) [INFO] Determining fastest mirrors
* 04-04:29:04 (3372) [INFO]  * EA4: 208.100.0.204
* 04-04:29:04 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 04-04:29:04 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 04-04:29:04 (3372) [INFO]  * epel: mirror.dst.ca
* 04-04:29:04 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 04-04:29:28 (3372) [INFO] 
* 04-04:29:28 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 04-04:29:28 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 04-04:29:28 (3382) [INFO] 
* 04-04:29:28 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 04-04:29:28 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 04-04:29:28 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 04-04:29:28 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 04-04:29:29 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-04_04:29:29_modified_for_AlmaLinux_8.json
* 04-04:29:29 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 04-04:29:29 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 04-04:29:29 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 05-04:26:35 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 05-04:26:37 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 05-04:26:37 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 05-04:26:37 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 05-04:26:37 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 05-04:26:37 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 05-04:26:56 (2925) [INFO] Checking if your system is up to date: 
* 05-04:26:56 (3361) [INFO] Running: /usr/bin/yum clean all
* 05-04:26:56 (3362) [INFO] 
* 05-04:26:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:26:57 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 05-04:26:57 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 05-04:26:57 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 05-04:26:57 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 05-04:26:57 (3372) [INFO]               : zabbix zabbix-non-supported
* 05-04:26:57 (3372) [INFO] Cleaning up list of fastest mirrors
* 05-04:26:57 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 05-04:26:57 (3382) [INFO] 
* 05-04:26:57 (3361) [INFO] Running: /usr/bin/yum check-update
* 05-04:26:57 (3362) [INFO] 
* 05-04:26:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:26:58 (3372) [INFO] Determining fastest mirrors
* 05-04:27:03 (3372) [INFO]  * EA4: 208.100.0.204
* 05-04:27:03 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 05-04:27:03 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 05-04:27:03 (3372) [INFO]  * epel: mirror.xenyth.net
* 05-04:27:03 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 05-04:27:31 (3372) [INFO] 
* 05-04:27:31 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 05-04:27:31 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 05-04:27:31 (3382) [INFO] 
* 05-04:27:31 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 05-04:27:31 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 05-04:27:33 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 05-04:27:33 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 05-04:27:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-05_04:27:35_modified_for_AlmaLinux_8.json
* 05-04:27:38 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 05-04:27:39 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 05-04:27:39 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 06-04:28:22 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 06-04:28:25 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 06-04:28:25 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 06-04:28:25 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 06-04:28:25 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 06-04:28:25 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 06-04:28:41 (2925) [INFO] Checking if your system is up to date: 
* 06-04:28:41 (3361) [INFO] Running: /usr/bin/yum clean all
* 06-04:28:41 (3362) [INFO] 
* 06-04:28:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:28:41 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 06-04:28:41 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 06-04:28:41 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 06-04:28:41 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 06-04:28:41 (3372) [INFO]               : zabbix zabbix-non-supported
* 06-04:28:42 (3372) [INFO] Cleaning up list of fastest mirrors
* 06-04:28:42 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 06-04:28:42 (3382) [INFO] 
* 06-04:28:42 (3361) [INFO] Running: /usr/bin/yum check-update
* 06-04:28:42 (3362) [INFO] 
* 06-04:28:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:28:43 (3372) [INFO] Determining fastest mirrors
* 06-04:28:48 (3372) [INFO]  * EA4: 208.100.0.204
* 06-04:28:48 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 06-04:28:48 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 06-04:28:48 (3372) [INFO]  * epel: mirror.dst.ca
* 06-04:28:48 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 06-04:29:09 (3372) [INFO] 
* 06-04:29:09 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 06-04:29:09 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 06-04:29:10 (3382) [INFO] 
* 06-04:29:10 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 06-04:29:10 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 06-04:29:10 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 06-04:29:10 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 06-04:29:10 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-06_04:29:10_modified_for_AlmaLinux_8.json
* 06-04:29:10 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 06-04:29:11 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 06-04:29:11 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 07-04:27:01 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 07-04:27:07 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 07-04:27:07 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 07-04:27:07 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 07-04:27:07 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 07-04:27:07 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 07-04:27:28 (2925) [INFO] Checking if your system is up to date: 
* 07-04:27:28 (3361) [INFO] Running: /usr/bin/yum clean all
* 07-04:27:28 (3362) [INFO] 
* 07-04:27:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:27:29 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 07-04:27:29 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 07-04:27:29 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 07-04:27:29 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 07-04:27:29 (3372) [INFO]               : zabbix zabbix-non-supported
* 07-04:27:29 (3372) [INFO] Cleaning up list of fastest mirrors
* 07-04:27:29 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 07-04:27:29 (3382) [INFO] 
* 07-04:27:29 (3361) [INFO] Running: /usr/bin/yum check-update
* 07-04:27:29 (3362) [INFO] 
* 07-04:27:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:27:29 (3372) [INFO] Determining fastest mirrors
* 07-04:27:34 (3372) [INFO]  * EA4: 208.100.0.204
* 07-04:27:34 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 07-04:27:34 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 07-04:27:34 (3372) [INFO]  * epel: mirror.dst.ca
* 07-04:27:34 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 07-04:27:58 (3372) [INFO] 
* 07-04:27:58 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 07-04:27:58 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 07-04:27:58 (3382) [INFO] 
* 07-04:27:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 07-04:27:58 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 07-04:27:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 07-04:27:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 07-04:28:00 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-07_04:28:00_modified_for_AlmaLinux_8.json
* 07-04:28:00 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 07-04:28:00 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 07-04:28:00 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 08-04:28:38 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 08-04:28:41 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 08-04:28:41 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 08-04:28:41 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 08-04:28:41 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 08-04:28:41 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 08-04:29:00 (2925) [INFO] Checking if your system is up to date: 
* 08-04:29:00 (3361) [INFO] Running: /usr/bin/yum clean all
* 08-04:29:00 (3362) [INFO] 
* 08-04:29:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:29:00 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 08-04:29:00 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 08-04:29:00 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 08-04:29:00 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 08-04:29:00 (3372) [INFO]               : zabbix zabbix-non-supported
* 08-04:29:00 (3372) [INFO] Cleaning up list of fastest mirrors
* 08-04:29:00 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 08-04:29:00 (3382) [INFO] 
* 08-04:29:00 (3361) [INFO] Running: /usr/bin/yum check-update
* 08-04:29:00 (3362) [INFO] 
* 08-04:29:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:29:01 (3372) [INFO] Determining fastest mirrors
* 08-04:29:06 (3372) [INFO]  * EA4: 208.100.0.204
* 08-04:29:06 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 08-04:29:06 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 08-04:29:06 (3372) [INFO]  * epel: mirror.dst.ca
* 08-04:29:06 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 08-04:29:26 (3372) [INFO] 
* 08-04:29:26 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 08-04:29:26 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 08-04:29:26 (3382) [INFO] 
* 08-04:29:26 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 08-04:29:26 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 08-04:29:26 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 08-04:29:26 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 08-04:29:27 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-08_04:29:27_modified_for_AlmaLinux_8.json
* 08-04:29:27 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 08-04:29:28 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 08-04:29:28 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 09-04:26:49 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 09-04:26:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 09-04:26:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 09-04:26:53 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 09-04:26:53 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 09-04:26:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 09-04:27:08 (2925) [INFO] Checking if your system is up to date: 
* 09-04:27:08 (3361) [INFO] Running: /usr/bin/yum clean all
* 09-04:27:08 (3362) [INFO] 
* 09-04:27:08 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 09-04:27:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 09-04:27:09 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 09-04:27:09 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 09-04:27:09 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 09-04:27:09 (3372) [INFO]               : zabbix zabbix-non-supported
* 09-04:27:09 (3372) [INFO] Cleaning up list of fastest mirrors
* 09-04:27:09 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 09-04:27:09 (3382) [INFO] 
* 09-04:27:09 (3361) [INFO] Running: /usr/bin/yum check-update
* 09-04:27:09 (3362) [INFO] 
* 09-04:27:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 09-04:27:09 (3372) [INFO] Determining fastest mirrors
* 09-04:27:14 (3372) [INFO]  * EA4: 208.100.0.204
* 09-04:27:14 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 09-04:27:14 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 09-04:27:14 (3372) [INFO]  * epel: mirror.dst.ca
* 09-04:27:14 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 09-04:27:35 (3372) [INFO] 
* 09-04:27:35 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 09-04:27:35 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 09-04:27:36 (3382) [INFO] 
* 09-04:27:36 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 09-04:27:36 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 09-04:27:36 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 09-04:27:36 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 09-04:27:37 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-09_04:27:37_modified_for_AlmaLinux_8.json
* 09-04:27:37 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 09-04:27:37 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 09-04:27:37 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 10-04:27:30 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 10-04:27:32 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 10-04:27:32 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 10-04:27:32 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 10-04:27:32 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 10-04:27:32 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 10-04:27:47 (2925) [INFO] Checking if your system is up to date: 
* 10-04:27:47 (3361) [INFO] Running: /usr/bin/yum clean all
* 10-04:27:47 (3362) [INFO] 
* 10-04:27:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:27:47 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 10-04:27:47 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 10-04:27:47 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 10-04:27:47 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 10-04:27:47 (3372) [INFO]               : zabbix zabbix-non-supported
* 10-04:27:48 (3372) [INFO] Cleaning up list of fastest mirrors
* 10-04:27:48 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 10-04:27:48 (3382) [INFO] 
* 10-04:27:48 (3361) [INFO] Running: /usr/bin/yum check-update
* 10-04:27:48 (3362) [INFO] 
* 10-04:27:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:27:48 (3372) [INFO] Determining fastest mirrors
* 10-04:27:52 (3372) [INFO]  * EA4: 208.100.0.204
* 10-04:27:52 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 10-04:27:52 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 10-04:27:52 (3372) [INFO]  * epel: mirror.dst.ca
* 10-04:27:52 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 10-04:28:17 (3372) [INFO] 
* 10-04:28:17 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 10-04:28:17 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 10-04:28:17 (3382) [INFO] 
* 10-04:28:17 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 10-04:28:17 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 10-04:28:17 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 10-04:28:17 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 10-04:28:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-10_04:28:18_modified_for_AlmaLinux_8.json
* 10-04:28:18 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 10-04:28:18 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 10-04:28:18 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 11-04:32:08 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 11-04:32:19 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 11-04:32:19 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 11-04:32:19 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 11-04:32:19 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 11-04:32:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 11-04:32:39 (2925) [INFO] Checking if your system is up to date: 
* 11-04:32:39 (3361) [INFO] Running: /usr/bin/yum clean all
* 11-04:32:39 (3362) [INFO] 
* 11-04:32:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:32:39 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 11-04:32:39 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 11-04:32:39 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 11-04:32:39 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 11-04:32:39 (3372) [INFO]               : zabbix zabbix-non-supported
* 11-04:32:40 (3372) [INFO] Cleaning up list of fastest mirrors
* 11-04:32:40 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 11-04:32:40 (3382) [INFO] 
* 11-04:32:40 (3361) [INFO] Running: /usr/bin/yum check-update
* 11-04:32:40 (3362) [INFO] 
* 11-04:32:40 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:32:41 (3372) [INFO] Determining fastest mirrors
* 11-04:32:44 (3372) [INFO]  * EA4: 208.100.0.204
* 11-04:32:44 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 11-04:32:44 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 11-04:32:44 (3372) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 11-04:32:44 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 11-04:33:08 (3372) [INFO] 
* 11-04:33:08 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 11-04:33:08 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 11-04:33:08 (3382) [INFO] 
* 11-04:33:08 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 11-04:33:08 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 11-04:33:08 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 11-04:33:08 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 11-04:33:10 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-11_04:33:09_modified_for_AlmaLinux_8.json
* 11-04:33:10 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 11-04:33:10 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 11-04:33:10 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 12-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 12-04:27:52 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 12-04:27:52 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 12-04:27:52 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 12-04:27:52 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 12-04:27:52 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 12-04:28:12 (2925) [INFO] Checking if your system is up to date: 
* 12-04:28:12 (3361) [INFO] Running: /usr/bin/yum clean all
* 12-04:28:12 (3362) [INFO] 
* 12-04:28:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:28:12 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 12-04:28:12 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 12-04:28:12 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 12-04:28:12 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 12-04:28:12 (3372) [INFO]               : zabbix zabbix-non-supported
* 12-04:28:12 (3372) [INFO] Cleaning up list of fastest mirrors
* 12-04:28:12 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 12-04:28:12 (3382) [INFO] 
* 12-04:28:12 (3361) [INFO] Running: /usr/bin/yum check-update
* 12-04:28:12 (3362) [INFO] 
* 12-04:28:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:28:13 (3372) [INFO] Determining fastest mirrors
* 12-04:28:17 (3372) [INFO]  * EA4: 208.100.0.204
* 12-04:28:17 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 12-04:28:17 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 12-04:28:17 (3372) [INFO]  * epel: mirror.dst.ca
* 12-04:28:17 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 12-04:28:43 (3372) [INFO] 
* 12-04:28:43 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 12-04:28:43 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 12-04:28:44 (3382) [INFO] 
* 12-04:28:44 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 12-04:28:44 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 12-04:28:44 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 12-04:28:44 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 12-04:28:48 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-12_04:28:47_modified_for_AlmaLinux_8.json
* 12-04:28:49 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 12-04:28:49 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 12-04:28:49 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 13-04:27:01 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 13-04:27:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 13-04:27:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 13-04:27:06 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 13-04:27:06 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 13-04:27:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 13-04:27:25 (2925) [INFO] Checking if your system is up to date: 
* 13-04:27:25 (3361) [INFO] Running: /usr/bin/yum clean all
* 13-04:27:25 (3362) [INFO] 
* 13-04:27:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:27:26 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 13-04:27:26 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 13-04:27:26 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 13-04:27:26 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 13-04:27:26 (3372) [INFO]               : zabbix zabbix-non-supported
* 13-04:27:26 (3372) [INFO] Cleaning up list of fastest mirrors
* 13-04:27:26 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 13-04:27:26 (3382) [INFO] 
* 13-04:27:26 (3361) [INFO] Running: /usr/bin/yum check-update
* 13-04:27:26 (3362) [INFO] 
* 13-04:27:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:27:27 (3372) [INFO] Determining fastest mirrors
* 13-04:27:31 (3372) [INFO]  * EA4: 208.100.0.204
* 13-04:27:31 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 13-04:27:31 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 13-04:27:31 (3372) [INFO]  * epel: mirror.dst.ca
* 13-04:27:31 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 13-04:27:56 (3372) [INFO] 
* 13-04:27:56 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 13-04:27:56 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 13-04:27:57 (3382) [INFO] 
* 13-04:27:57 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 13-04:27:57 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 13-04:27:57 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 13-04:27:57 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 13-04:27:58 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-13_04:27:58_modified_for_AlmaLinux_8.json
* 13-04:27:58 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 13-04:27:58 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 13-04:27:58 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 14-04:27:38 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 14-04:27:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 14-04:27:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 14-04:27:40 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 14-04:27:40 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 14-04:27:40 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 14-04:27:57 (2925) [INFO] Checking if your system is up to date: 
* 14-04:27:57 (3361) [INFO] Running: /usr/bin/yum clean all
* 14-04:27:57 (3362) [INFO] 
* 14-04:27:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:27:57 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 14-04:27:57 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 14-04:27:57 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 14-04:27:57 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 14-04:27:57 (3372) [INFO]               : zabbix zabbix-non-supported
* 14-04:27:57 (3372) [INFO] Cleaning up list of fastest mirrors
* 14-04:27:57 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 14-04:27:58 (3382) [INFO] 
* 14-04:27:58 (3361) [INFO] Running: /usr/bin/yum check-update
* 14-04:27:58 (3362) [INFO] 
* 14-04:27:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:27:58 (3372) [INFO] Determining fastest mirrors
* 14-04:28:05 (3372) [INFO]  * EA4: 208.100.0.204
* 14-04:28:05 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 14-04:28:05 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 14-04:28:05 (3372) [INFO]  * epel: mirror.dst.ca
* 14-04:28:05 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 14-04:28:27 (3372) [INFO] 
* 14-04:28:27 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 14-04:28:27 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 14-04:28:27 (3382) [INFO] 
* 14-04:28:27 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 14-04:28:27 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 14-04:28:27 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 14-04:28:27 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 14-04:28:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-14_04:28:28_modified_for_AlmaLinux_8.json
* 14-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 14-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 14-04:28:28 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 15-04:28:14 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 15-04:28:16 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 15-04:28:16 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 15-04:28:16 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 15-04:28:16 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 15-04:28:16 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 15-04:28:30 (2925) [INFO] Checking if your system is up to date: 
* 15-04:28:30 (3361) [INFO] Running: /usr/bin/yum clean all
* 15-04:28:30 (3362) [INFO] 
* 15-04:28:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:28:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 15-04:28:30 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 15-04:28:30 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 15-04:28:30 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 15-04:28:30 (3372) [INFO]               : zabbix zabbix-non-supported
* 15-04:28:30 (3372) [INFO] Cleaning up list of fastest mirrors
* 15-04:28:30 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 15-04:28:30 (3382) [INFO] 
* 15-04:28:30 (3361) [INFO] Running: /usr/bin/yum check-update
* 15-04:28:30 (3362) [INFO] 
* 15-04:28:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:28:31 (3372) [INFO] Determining fastest mirrors
* 15-04:28:35 (3372) [INFO]  * EA4: 208.100.0.204
* 15-04:28:35 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 15-04:28:35 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 15-04:28:35 (3372) [INFO]  * epel: mirror.xenyth.net
* 15-04:28:35 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 15-04:29:02 (3372) [INFO] 
* 15-04:29:02 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 15-04:29:02 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 15-04:29:02 (3382) [INFO] 
* 15-04:29:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 15-04:29:02 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 15-04:29:02 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 15-04:29:02 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 15-04:29:04 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-15_04:29:04_modified_for_AlmaLinux_8.json
* 15-04:29:04 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 15-04:29:04 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 15-04:29:04 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 16-04:27:27 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 16-04:27:31 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 16-04:27:31 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 16-04:27:31 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 16-04:27:31 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 16-04:27:31 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 16-04:27:53 (2925) [INFO] Checking if your system is up to date: 
* 16-04:27:53 (3361) [INFO] Running: /usr/bin/yum clean all
* 16-04:27:53 (3362) [INFO] 
* 16-04:27:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:27:53 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 16-04:27:53 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 16-04:27:53 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 16-04:27:53 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 16-04:27:53 (3372) [INFO]               : zabbix zabbix-non-supported
* 16-04:27:53 (3372) [INFO] Cleaning up list of fastest mirrors
* 16-04:27:53 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 16-04:27:53 (3382) [INFO] 
* 16-04:27:53 (3361) [INFO] Running: /usr/bin/yum check-update
* 16-04:27:53 (3362) [INFO] 
* 16-04:27:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:27:54 (3372) [INFO] Determining fastest mirrors
* 16-04:28:00 (3372) [INFO]  * EA4: 63.247.64.58
* 16-04:28:00 (3372) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 16-04:28:00 (3372) [INFO]  * cpanel-plugins: 63.247.64.58
* 16-04:28:00 (3372) [INFO]  * epel: mirror.dst.ca
* 16-04:28:00 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 16-04:28:20 (3372) [INFO] 
* 16-04:28:20 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 16-04:28:20 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 16-04:28:21 (3382) [INFO] 
* 16-04:28:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 16-04:28:21 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 16-04:28:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 16-04:28:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 16-04:28:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-16_04:28:22_modified_for_AlmaLinux_8.json
* 16-04:28:22 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 16-04:28:22 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 16-04:28:22 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 17-04:30:16 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 17-04:30:22 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 17-04:30:22 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 17-04:30:22 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 17-04:30:22 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 17-04:30:22 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 17-04:30:40 (2925) [INFO] Checking if your system is up to date: 
* 17-04:30:40 (3361) [INFO] Running: /usr/bin/yum clean all
* 17-04:30:40 (3362) [INFO] 
* 17-04:30:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:30:41 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 17-04:30:41 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 17-04:30:41 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 17-04:30:41 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 17-04:30:41 (3372) [INFO]               : zabbix zabbix-non-supported
* 17-04:30:41 (3372) [INFO] Cleaning up list of fastest mirrors
* 17-04:30:41 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 17-04:30:41 (3382) [INFO] 
* 17-04:30:41 (3361) [INFO] Running: /usr/bin/yum check-update
* 17-04:30:41 (3362) [INFO] 
* 17-04:30:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:30:42 (3372) [INFO] Determining fastest mirrors
* 17-04:30:45 (3372) [INFO]  * EA4: 208.100.0.204
* 17-04:30:45 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 17-04:30:45 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 17-04:30:45 (3372) [INFO]  * epel: mirror.dst.ca
* 17-04:30:45 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 17-04:31:09 (3372) [INFO] 
* 17-04:31:09 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 17-04:31:09 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 17-04:31:09 (3382) [INFO] 
* 17-04:31:09 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 17-04:31:09 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 17-04:31:09 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 17-04:31:09 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 17-04:31:10 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-17_04:31:10_modified_for_AlmaLinux_8.json
* 17-04:31:10 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 17-04:31:10 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 17-04:31:10 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 18-04:32:19 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 18-04:32:29 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 18-04:32:29 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 18-04:32:29 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 18-04:32:29 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 18-04:32:29 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 18-04:32:47 (2925) [INFO] Checking if your system is up to date: 
* 18-04:32:47 (3361) [INFO] Running: /usr/bin/yum clean all
* 18-04:32:47 (3362) [INFO] 
* 18-04:32:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:32:47 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 18-04:32:47 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 18-04:32:47 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 18-04:32:47 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 18-04:32:47 (3372) [INFO]               : zabbix zabbix-non-supported
* 18-04:32:47 (3372) [INFO] Cleaning up list of fastest mirrors
* 18-04:32:47 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 18-04:32:47 (3382) [INFO] 
* 18-04:32:47 (3361) [INFO] Running: /usr/bin/yum check-update
* 18-04:32:47 (3362) [INFO] 
* 18-04:32:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:32:48 (3372) [INFO] Determining fastest mirrors
* 18-04:32:53 (3372) [INFO]  * EA4: 208.100.0.204
* 18-04:32:53 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 18-04:32:53 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 18-04:32:53 (3372) [INFO]  * epel: mirror.dst.ca
* 18-04:32:53 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 18-04:33:16 (3372) [INFO] 
* 18-04:33:16 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 18-04:33:16 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 18-04:33:16 (3382) [INFO] 
* 18-04:33:16 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 18-04:33:16 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 18-04:33:16 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 18-04:33:16 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 18-04:33:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-18_04:33:21_modified_for_AlmaLinux_8.json
* 18-04:33:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 18-04:33:23 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 18-04:33:23 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 19-04:26:48 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 19-04:26:51 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 19-04:26:51 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 19-04:26:51 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 19-04:26:51 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 19-04:26:51 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 19-04:27:06 (2925) [INFO] Checking if your system is up to date: 
* 19-04:27:06 (3361) [INFO] Running: /usr/bin/yum clean all
* 19-04:27:06 (3362) [INFO] 
* 19-04:27:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:27:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 19-04:27:06 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 19-04:27:06 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 19-04:27:06 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 19-04:27:06 (3372) [INFO]               : zabbix zabbix-non-supported
* 19-04:27:07 (3372) [INFO] Cleaning up list of fastest mirrors
* 19-04:27:07 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 19-04:27:07 (3382) [INFO] 
* 19-04:27:07 (3361) [INFO] Running: /usr/bin/yum check-update
* 19-04:27:07 (3362) [INFO] 
* 19-04:27:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:27:07 (3372) [INFO] Determining fastest mirrors
* 19-04:27:11 (3372) [INFO]  * EA4: 208.100.0.204
* 19-04:27:11 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 19-04:27:11 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 19-04:27:11 (3372) [INFO]  * epel: mirror.dst.ca
* 19-04:27:11 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 19-04:27:33 (3372) [INFO] 
* 19-04:27:33 (3372) [INFO] kernel.x86_64                     3.10.0-1160.80.1.el7                   updates
* 19-04:27:33 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 19-04:27:34 (3382) [INFO] 
* 19-04:27:34 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 19-04:27:34 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 19-04:27:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 19-04:27:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 19-04:27:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-19_04:27:35_modified_for_AlmaLinux_8.json
* 19-04:27:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 19-04:27:35 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 19-04:27:35 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 20-04:28:48 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 20-04:28:50 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 20-04:28:50 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 20-04:28:50 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 20-04:28:50 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 20-04:28:50 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 20-04:29:08 (2925) [INFO] Checking if your system is up to date: 
* 20-04:29:08 (3361) [INFO] Running: /usr/bin/yum clean all
* 20-04:29:08 (3362) [INFO] 
* 20-04:29:08 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:29:08 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 20-04:29:08 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 20-04:29:08 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 20-04:29:08 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 20-04:29:08 (3372) [INFO]               : zabbix zabbix-non-supported
* 20-04:29:09 (3372) [INFO] Cleaning up list of fastest mirrors
* 20-04:29:09 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 20-04:29:09 (3382) [INFO] 
* 20-04:29:09 (3361) [INFO] Running: /usr/bin/yum check-update
* 20-04:29:09 (3362) [INFO] 
* 20-04:29:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:29:09 (3372) [INFO] Determining fastest mirrors
* 20-04:29:14 (3372) [INFO]  * EA4: 208.100.0.204
* 20-04:29:14 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 20-04:29:14 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 20-04:29:14 (3372) [INFO]  * epel: mirror.dst.ca
* 20-04:29:14 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 20-04:29:40 (3372) [INFO] 
* 20-04:29:40 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 20-04:29:40 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 20-04:29:41 (3382) [INFO] 
* 20-04:29:41 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 20-04:29:41 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 20-04:29:41 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 20-04:29:41 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 20-04:29:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-20_04:29:45_modified_for_AlmaLinux_8.json
* 20-04:29:48 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 20-04:29:48 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 20-04:29:48 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 21-04:26:55 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 21-04:27:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 21-04:27:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 21-04:27:01 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 21-04:27:01 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 21-04:27:01 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 21-04:27:18 (2925) [INFO] Checking if your system is up to date: 
* 21-04:27:18 (3361) [INFO] Running: /usr/bin/yum clean all
* 21-04:27:18 (3362) [INFO] 
* 21-04:27:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:27:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 21-04:27:18 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 21-04:27:18 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 21-04:27:18 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 21-04:27:18 (3372) [INFO]               : zabbix zabbix-non-supported
* 21-04:27:19 (3372) [INFO] Cleaning up list of fastest mirrors
* 21-04:27:19 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 21-04:27:19 (3382) [INFO] 
* 21-04:27:19 (3361) [INFO] Running: /usr/bin/yum check-update
* 21-04:27:19 (3362) [INFO] 
* 21-04:27:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:27:19 (3372) [INFO] Determining fastest mirrors
* 21-04:27:22 (3372) [INFO]  * EA4: 208.100.0.204
* 21-04:27:22 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 21-04:27:22 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 21-04:27:22 (3372) [INFO]  * epel: mirror.dst.ca
* 21-04:27:22 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 21-04:27:45 (3372) [INFO] 
* 21-04:27:45 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 21-04:27:45 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 21-04:27:45 (3382) [INFO] 
* 21-04:27:45 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 21-04:27:45 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 21-04:27:45 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 21-04:27:45 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 21-04:27:46 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-21_04:27:46_modified_for_AlmaLinux_8.json
* 21-04:27:46 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 21-04:27:46 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 21-04:27:46 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 22-04:30:32 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 22-04:30:35 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 22-04:30:35 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 22-04:30:35 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 22-04:30:35 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 22-04:30:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 22-04:30:52 (2925) [INFO] Checking if your system is up to date: 
* 22-04:30:52 (3361) [INFO] Running: /usr/bin/yum clean all
* 22-04:30:52 (3362) [INFO] 
* 22-04:30:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:30:52 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 22-04:30:52 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 22-04:30:52 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 22-04:30:52 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 22-04:30:52 (3372) [INFO]               : zabbix zabbix-non-supported
* 22-04:30:53 (3372) [INFO] Cleaning up list of fastest mirrors
* 22-04:30:53 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 22-04:30:53 (3382) [INFO] 
* 22-04:30:53 (3361) [INFO] Running: /usr/bin/yum check-update
* 22-04:30:53 (3362) [INFO] 
* 22-04:30:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:30:53 (3372) [INFO] Determining fastest mirrors
* 22-04:30:58 (3372) [INFO]  * EA4: 208.100.0.204
* 22-04:30:58 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 22-04:30:58 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 22-04:30:58 (3372) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 22-04:30:58 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 22-04:31:22 (3372) [INFO] 
* 22-04:31:22 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 22-04:31:22 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 22-04:31:22 (3382) [INFO] 
* 22-04:31:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 22-04:31:22 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 22-04:31:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 22-04:31:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 22-04:31:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-22_04:31:23_modified_for_AlmaLinux_8.json
* 22-04:31:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 22-04:31:23 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 22-04:31:23 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 23-04:27:00 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 23-04:27:05 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 23-04:27:05 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 23-04:27:05 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 23-04:27:05 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 23-04:27:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 23-04:27:22 (2925) [INFO] Checking if your system is up to date: 
* 23-04:27:22 (3361) [INFO] Running: /usr/bin/yum clean all
* 23-04:27:22 (3362) [INFO] 
* 23-04:27:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:27:22 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 23-04:27:22 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 23-04:27:22 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 23-04:27:22 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 23-04:27:22 (3372) [INFO]               : zabbix zabbix-non-supported
* 23-04:27:23 (3372) [INFO] Cleaning up list of fastest mirrors
* 23-04:27:23 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 23-04:27:23 (3382) [INFO] 
* 23-04:27:23 (3361) [INFO] Running: /usr/bin/yum check-update
* 23-04:27:23 (3362) [INFO] 
* 23-04:27:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:27:23 (3372) [INFO] Determining fastest mirrors
* 23-04:27:29 (3372) [INFO]  * EA4: 208.100.0.204
* 23-04:27:29 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 23-04:27:29 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 23-04:27:29 (3372) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 23-04:27:29 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 23-04:27:57 (3372) [INFO] 
* 23-04:27:57 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 23-04:27:57 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 23-04:27:58 (3382) [INFO] 
* 23-04:27:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 23-04:27:58 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 23-04:27:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 23-04:27:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 23-04:27:59 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-23_04:27:59_modified_for_AlmaLinux_8.json
* 23-04:27:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 23-04:27:59 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 23-04:27:59 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 24-04:27:54 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 24-04:27:57 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 24-04:27:57 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 24-04:27:57 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 24-04:27:57 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 24-04:27:57 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 24-04:28:10 (2925) [INFO] Checking if your system is up to date: 
* 24-04:28:10 (3361) [INFO] Running: /usr/bin/yum clean all
* 24-04:28:10 (3362) [INFO] 
* 24-04:28:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:28:10 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 24-04:28:10 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 24-04:28:10 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 24-04:28:10 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 24-04:28:10 (3372) [INFO]               : zabbix zabbix-non-supported
* 24-04:28:11 (3372) [INFO] Cleaning up list of fastest mirrors
* 24-04:28:11 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 24-04:28:11 (3382) [INFO] 
* 24-04:28:11 (3361) [INFO] Running: /usr/bin/yum check-update
* 24-04:28:11 (3362) [INFO] 
* 24-04:28:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:28:11 (3372) [INFO] Determining fastest mirrors
* 24-04:28:16 (3372) [INFO]  * EA4: 208.100.0.204
* 24-04:28:16 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 24-04:28:16 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 24-04:28:16 (3372) [INFO]  * epel: mirror.dst.ca
* 24-04:28:16 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 24-04:28:40 (3372) [INFO] 
* 24-04:28:40 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 24-04:28:40 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 24-04:28:40 (3382) [INFO] 
* 24-04:28:40 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 24-04:28:40 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 24-04:28:40 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 24-04:28:40 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 24-04:28:41 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-24_04:28:41_modified_for_AlmaLinux_8.json
* 24-04:28:41 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 24-04:28:41 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 24-04:28:41 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 25-04:31:51 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 25-04:32:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 25-04:32:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 25-04:32:01 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 25-04:32:01 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 25-04:32:01 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 25-04:32:22 (2925) [INFO] Checking if your system is up to date: 
* 25-04:32:22 (3361) [INFO] Running: /usr/bin/yum clean all
* 25-04:32:22 (3362) [INFO] 
* 25-04:32:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:32:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 25-04:32:23 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 25-04:32:23 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 25-04:32:23 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 25-04:32:23 (3372) [INFO]               : zabbix zabbix-non-supported
* 25-04:32:23 (3372) [INFO] Cleaning up list of fastest mirrors
* 25-04:32:23 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 25-04:32:23 (3382) [INFO] 
* 25-04:32:23 (3361) [INFO] Running: /usr/bin/yum check-update
* 25-04:32:23 (3362) [INFO] 
* 25-04:32:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:32:24 (3372) [INFO] Determining fastest mirrors
* 25-04:32:29 (3372) [INFO]  * EA4: 208.100.0.204
* 25-04:32:29 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 25-04:32:29 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 25-04:32:29 (3372) [INFO]  * epel: mirror.dst.ca
* 25-04:32:29 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 25-04:32:54 (3372) [INFO] 
* 25-04:32:54 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 25-04:32:54 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 25-04:32:55 (3382) [INFO] 
* 25-04:32:55 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 25-04:32:55 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 25-04:32:55 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 25-04:32:55 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 25-04:33:04 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-25_04:33:04_modified_for_AlmaLinux_8.json
* 25-04:33:04 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 25-04:33:05 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 25-04:33:05 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 26-04:26:54 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 26-04:27:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 26-04:27:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 26-04:27:01 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 26-04:27:01 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 26-04:27:01 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 26-04:27:15 (2925) [INFO] Checking if your system is up to date: 
* 26-04:27:15 (3361) [INFO] Running: /usr/bin/yum clean all
* 26-04:27:15 (3362) [INFO] 
* 26-04:27:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:27:15 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 26-04:27:15 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 26-04:27:15 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 26-04:27:15 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 26-04:27:15 (3372) [INFO]               : zabbix zabbix-non-supported
* 26-04:27:15 (3372) [INFO] Cleaning up list of fastest mirrors
* 26-04:27:15 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 26-04:27:16 (3382) [INFO] 
* 26-04:27:16 (3361) [INFO] Running: /usr/bin/yum check-update
* 26-04:27:16 (3362) [INFO] 
* 26-04:27:16 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:27:16 (3372) [INFO] Determining fastest mirrors
* 26-04:27:19 (3372) [INFO]  * EA4: 208.100.0.204
* 26-04:27:19 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 26-04:27:19 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 26-04:27:19 (3372) [INFO]  * epel: mirror.dst.ca
* 26-04:27:19 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 26-04:27:44 (3372) [INFO] 
* 26-04:27:44 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 26-04:27:44 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 26-04:27:44 (3382) [INFO] 
* 26-04:27:44 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 26-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 26-04:27:44 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 26-04:27:44 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 26-04:27:45 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-26_04:27:45_modified_for_AlmaLinux_8.json
* 26-04:27:45 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 26-04:27:45 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 26-04:27:45 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 27-04:28:08 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 27-04:28:21 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 27-04:28:21 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 27-04:28:21 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 27-04:28:21 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 27-04:28:21 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 27-04:28:48 (2925) [INFO] Checking if your system is up to date: 
* 27-04:28:48 (3361) [INFO] Running: /usr/bin/yum clean all
* 27-04:28:48 (3362) [INFO] 
* 27-04:28:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:28:49 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 27-04:28:49 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 27-04:28:49 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 27-04:28:49 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 27-04:28:49 (3372) [INFO]               : zabbix zabbix-non-supported
* 27-04:28:49 (3372) [INFO] Cleaning up list of fastest mirrors
* 27-04:28:49 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 27-04:28:49 (3382) [INFO] 
* 27-04:28:49 (3361) [INFO] Running: /usr/bin/yum check-update
* 27-04:28:49 (3362) [INFO] 
* 27-04:28:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:28:50 (3372) [INFO] Determining fastest mirrors
* 27-04:28:55 (3372) [INFO]  * EA4: 208.100.0.204
* 27-04:28:55 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 27-04:28:55 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 27-04:28:55 (3372) [INFO]  * epel: mirror.dst.ca
* 27-04:28:55 (3372) [INFO]  * remi-safe: mirror.usi.edu
* 27-04:29:20 (3372) [INFO] 
* 27-04:29:20 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 27-04:29:20 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 27-04:29:20 (3382) [INFO] 
* 27-04:29:20 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 27-04:29:20 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 27-04:29:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 27-04:29:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 27-04:29:24 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-27_04:29:24_modified_for_AlmaLinux_8.json
* 27-04:29:24 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 27-04:29:24 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 27-04:29:24 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 28-04:27:21 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 28-04:27:28 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 28-04:27:28 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 28-04:27:28 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 28-04:27:28 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 28-04:27:28 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 28-04:27:49 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading
* 28-04:27:49 (3077) [ERROR] https://mirror.usi.edu/pub/remi/enterprise/7/safe/x86_64/repodata/5e02a79a4c931a1f3fcad0d4f9dfc8bbde25b18ec7f7b8b3a4bb34831b34b291-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.


* 28-04:27:49 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable

* 28-04:27:49 (2925) [INFO] Checking if your system is up to date: 
* 28-04:27:49 (3361) [INFO] Running: /usr/bin/yum clean all
* 28-04:27:49 (3362) [INFO] 
* 28-04:27:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:27:49 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 28-04:27:49 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 28-04:27:49 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 28-04:27:49 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 28-04:27:49 (3372) [INFO]               : zabbix zabbix-non-supported
* 28-04:27:50 (3372) [INFO] Cleaning up list of fastest mirrors
* 28-04:27:50 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 28-04:27:50 (3382) [INFO] 
* 28-04:27:50 (3361) [INFO] Running: /usr/bin/yum check-update
* 28-04:27:50 (3362) [INFO] 
* 28-04:27:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:27:50 (3372) [INFO] Determining fastest mirrors
* 28-04:28:02 (3372) [INFO]  * EA4: 208.100.0.204
* 28-04:28:02 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 28-04:28:02 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 28-04:28:02 (3372) [INFO]  * epel: mirror.xenyth.net
* 28-04:28:02 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 28-04:28:25 (3372) [INFO] 
* 28-04:28:25 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 28-04:28:25 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 28-04:28:25 (3382) [INFO] 
* 28-04:28:25 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 28-04:28:25 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 28-04:28:27 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 28-04:28:27 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 28-04:28:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-28_04:28:28_modified_for_AlmaLinux_8.json
* 28-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 28-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 28-04:28:28 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 29-04:27:11 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 29-04:27:19 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 29-04:27:19 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 29-04:27:19 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 29-04:27:19 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 29-04:27:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 29-04:27:39 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading
* 29-04:27:39 (3077) [ERROR] https://mirror.usi.edu/pub/remi/enterprise/7/safe/x86_64/repodata/5e02a79a4c931a1f3fcad0d4f9dfc8bbde25b18ec7f7b8b3a4bb34831b34b291-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.


* 29-04:27:39 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable

* 29-04:27:39 (2925) [INFO] Checking if your system is up to date: 
* 29-04:27:39 (3361) [INFO] Running: /usr/bin/yum clean all
* 29-04:27:39 (3362) [INFO] 
* 29-04:27:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 29-04:27:39 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 29-04:27:39 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 29-04:27:39 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 29-04:27:39 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 29-04:27:39 (3372) [INFO]               : zabbix zabbix-non-supported
* 29-04:27:40 (3372) [INFO] Cleaning up list of fastest mirrors
* 29-04:27:40 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 29-04:27:40 (3382) [INFO] 
* 29-04:27:40 (3361) [INFO] Running: /usr/bin/yum check-update
* 29-04:27:40 (3362) [INFO] 
* 29-04:27:40 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 29-04:27:40 (3372) [INFO] Determining fastest mirrors
* 29-04:27:45 (3372) [INFO]  * EA4: 208.100.0.204
* 29-04:27:45 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 29-04:27:45 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 29-04:27:45 (3372) [INFO]  * epel: mirror.dst.ca
* 29-04:27:45 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 29-04:28:07 (3372) [INFO] 
* 29-04:28:07 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 29-04:28:07 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 29-04:28:07 (3382) [INFO] 
* 29-04:28:07 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 29-04:28:07 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 29-04:28:10 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 29-04:28:11 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 29-04:28:15 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-29_04:28:15_modified_for_AlmaLinux_8.json
* 29-04:28:15 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 29-04:28:15 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 29-04:28:15 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 30-04:26:58 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 30-04:27:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 30-04:27:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 30-04:27:06 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 30-04:27:06 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 30-04:27:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 30-04:27:23 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading
* 30-04:27:23 (3077) [ERROR] https://mirror.usi.edu/pub/remi/enterprise/7/safe/x86_64/repodata/5e02a79a4c931a1f3fcad0d4f9dfc8bbde25b18ec7f7b8b3a4bb34831b34b291-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.


* 30-04:27:23 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable

* 30-04:27:23 (2925) [INFO] Checking if your system is up to date: 
* 30-04:27:23 (3361) [INFO] Running: /usr/bin/yum clean all
* 30-04:27:23 (3362) [INFO] 
* 30-04:27:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 30-04:27:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 30-04:27:23 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 30-04:27:23 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 30-04:27:23 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 30-04:27:23 (3372) [INFO]               : zabbix zabbix-non-supported
* 30-04:27:25 (3372) [INFO] Cleaning up list of fastest mirrors
* 30-04:27:25 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 30-04:27:25 (3382) [INFO] 
* 30-04:27:25 (3361) [INFO] Running: /usr/bin/yum check-update
* 30-04:27:25 (3362) [INFO] 
* 30-04:27:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 30-04:27:25 (3372) [INFO] Determining fastest mirrors
* 30-04:27:30 (3372) [INFO]  * EA4: 208.100.0.204
* 30-04:27:30 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 30-04:27:30 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 30-04:27:30 (3372) [INFO]  * epel: mirror.dst.ca
* 30-04:27:30 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 30-04:27:52 (3372) [INFO] 
* 30-04:27:52 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 30-04:27:52 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 30-04:27:53 (3382) [INFO] 
* 30-04:27:53 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 30-04:27:53 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 30-04:27:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 30-04:27:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 30-04:27:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-30_04:27:54_modified_for_AlmaLinux_8.json
* 30-04:27:54 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 30-04:27:54 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 30-04:27:54 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 31-04:29:20 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 31-04:29:23 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 31-04:29:23 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 31-04:29:23 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 31-04:29:23 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 31-04:29:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 31-04:29:37 (2925) [INFO] Checking if your system is up to date: 
* 31-04:29:37 (3361) [INFO] Running: /usr/bin/yum clean all
* 31-04:29:37 (3362) [INFO] 
* 31-04:29:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 31-04:29:37 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 31-04:29:37 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 31-04:29:37 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 31-04:29:37 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 31-04:29:37 (3372) [INFO]               : zabbix zabbix-non-supported
* 31-04:29:38 (3372) [INFO] Cleaning up list of fastest mirrors
* 31-04:29:38 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 31-04:29:38 (3382) [INFO] 
* 31-04:29:38 (3361) [INFO] Running: /usr/bin/yum check-update
* 31-04:29:38 (3362) [INFO] 
* 31-04:29:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 31-04:29:38 (3372) [INFO] Determining fastest mirrors
* 31-04:29:45 (3372) [INFO]  * EA4: 208.100.0.204
* 31-04:29:45 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 31-04:29:45 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 31-04:29:45 (3372) [INFO]  * epel: mirror.dst.ca
* 31-04:29:45 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 31-04:30:14 (3372) [INFO] 
* 31-04:30:14 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 31-04:30:14 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 31-04:30:14 (3382) [INFO] 
* 31-04:30:14 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 31-04:30:14 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 31-04:30:14 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 31-04:30:14 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 31-04:30:16 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-31_04:30:16_modified_for_AlmaLinux_8.json
* 31-04:30:16 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 31-04:30:16 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 31-04:30:16 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 01-04:27:51 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 01-04:27:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 01-04:27:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 01-04:27:59 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 01-04:27:59 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 01-04:27:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 01-04:28:15 (2925) [INFO] Checking if your system is up to date: 
* 01-04:28:15 (3361) [INFO] Running: /usr/bin/yum clean all
* 01-04:28:15 (3362) [INFO] 
* 01-04:28:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:28:15 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 01-04:28:15 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 01-04:28:15 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 01-04:28:15 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 01-04:28:15 (3372) [INFO]               : zabbix zabbix-non-supported
* 01-04:28:16 (3372) [INFO] Cleaning up list of fastest mirrors
* 01-04:28:16 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 01-04:28:16 (3382) [INFO] 
* 01-04:28:16 (3361) [INFO] Running: /usr/bin/yum check-update
* 01-04:28:16 (3362) [INFO] 
* 01-04:28:16 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:28:17 (3372) [INFO] Determining fastest mirrors
* 01-04:28:29 (3372) [INFO]  * EA4: 208.100.0.204
* 01-04:28:29 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 01-04:28:29 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 01-04:28:29 (3372) [INFO]  * epel: mirror.dst.ca
* 01-04:28:29 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 01-04:28:52 (3372) [INFO] 
* 01-04:28:52 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 01-04:28:52 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 01-04:28:53 (3382) [INFO] 
* 01-04:28:53 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 01-04:28:53 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 01-04:28:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 01-04:28:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 01-04:28:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-01_04:28:54_modified_for_AlmaLinux_8.json
* 01-04:28:54 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 01-04:28:54 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 01-04:28:54 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 02-04:27:12 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 02-04:27:20 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 02-04:27:20 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 02-04:27:20 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 02-04:27:20 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 02-04:27:20 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 02-04:27:36 (2925) [INFO] Checking if your system is up to date: 
* 02-04:27:36 (3361) [INFO] Running: /usr/bin/yum clean all
* 02-04:27:36 (3362) [INFO] 
* 02-04:27:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:27:37 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 02-04:27:37 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 02-04:27:37 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 02-04:27:37 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 02-04:27:37 (3372) [INFO]               : zabbix zabbix-non-supported
* 02-04:27:37 (3372) [INFO] Cleaning up list of fastest mirrors
* 02-04:27:37 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 02-04:27:38 (3382) [INFO] 
* 02-04:27:38 (3361) [INFO] Running: /usr/bin/yum check-update
* 02-04:27:38 (3362) [INFO] 
* 02-04:27:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:27:38 (3372) [INFO] Determining fastest mirrors
* 02-04:27:43 (3372) [INFO]  * EA4: 208.100.0.204
* 02-04:27:43 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 02-04:27:43 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 02-04:27:43 (3372) [INFO]  * epel: epel.mirror.constant.com
* 02-04:27:43 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 02-04:28:05 (3372) [INFO] 
* 02-04:28:05 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 02-04:28:05 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 02-04:28:05 (3382) [INFO] 
* 02-04:28:05 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 02-04:28:05 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 02-04:28:05 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 02-04:28:05 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 02-04:28:06 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-02_04:28:06_modified_for_AlmaLinux_8.json
* 02-04:28:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 02-04:28:07 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 02-04:28:07 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 03-04:27:32 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 03-04:27:34 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 03-04:27:34 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 03-04:27:34 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 03-04:27:34 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 03-04:27:34 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 03-04:27:50 (2925) [INFO] Checking if your system is up to date: 
* 03-04:27:50 (3361) [INFO] Running: /usr/bin/yum clean all
* 03-04:27:50 (3362) [INFO] 
* 03-04:27:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:27:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 03-04:27:51 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 03-04:27:51 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 03-04:27:51 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 03-04:27:51 (3372) [INFO]               : zabbix zabbix-non-supported
* 03-04:27:51 (3372) [INFO] Cleaning up list of fastest mirrors
* 03-04:27:51 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 03-04:27:51 (3382) [INFO] 
* 03-04:27:51 (3361) [INFO] Running: /usr/bin/yum check-update
* 03-04:27:51 (3362) [INFO] 
* 03-04:27:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:27:52 (3372) [INFO] Determining fastest mirrors
* 03-04:27:57 (3372) [INFO]  * EA4: 208.100.0.204
* 03-04:27:57 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 03-04:27:57 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 03-04:27:57 (3372) [INFO]  * epel: epel.mirror.constant.com
* 03-04:27:57 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 03-04:28:24 (3372) [INFO] 
* 03-04:28:24 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 03-04:28:24 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 03-04:28:24 (3382) [INFO] 
* 03-04:28:24 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 03-04:28:24 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 03-04:28:25 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 03-04:28:25 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 03-04:28:26 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-03_04:28:26_modified_for_AlmaLinux_8.json
* 03-04:28:26 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 03-04:28:26 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 03-04:28:26 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 04-04:26:57 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 04-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 04-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 04-04:26:59 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 04-04:26:59 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 04-04:26:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 04-04:27:15 (2925) [INFO] Checking if your system is up to date: 
* 04-04:27:15 (3361) [INFO] Running: /usr/bin/yum clean all
* 04-04:27:15 (3362) [INFO] 
* 04-04:27:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:27:15 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 04-04:27:15 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 04-04:27:15 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 04-04:27:15 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 04-04:27:15 (3372) [INFO]               : zabbix zabbix-non-supported
* 04-04:27:15 (3372) [INFO] Cleaning up list of fastest mirrors
* 04-04:27:15 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 04-04:27:16 (3382) [INFO] 
* 04-04:27:16 (3361) [INFO] Running: /usr/bin/yum check-update
* 04-04:27:16 (3362) [INFO] 
* 04-04:27:16 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:27:16 (3372) [INFO] Determining fastest mirrors
* 04-04:27:23 (3372) [INFO]  * EA4: 208.100.0.204
* 04-04:27:23 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 04-04:27:23 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 04-04:27:23 (3372) [INFO]  * epel: mirror.dst.ca
* 04-04:27:23 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 04-04:27:46 (3372) [INFO] 
* 04-04:27:46 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 04-04:27:46 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 04-04:27:47 (3382) [INFO] 
* 04-04:27:47 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 04-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 04-04:27:47 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 04-04:27:47 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 04-04:27:48 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-04_04:27:48_modified_for_AlmaLinux_8.json
* 04-04:27:48 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 04-04:27:48 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 04-04:27:48 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 05-04:29:57 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 05-04:30:00 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 05-04:30:00 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 05-04:30:00 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 05-04:30:00 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 05-04:30:00 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 05-04:30:18 (2925) [INFO] Checking if your system is up to date: 
* 05-04:30:18 (3361) [INFO] Running: /usr/bin/yum clean all
* 05-04:30:18 (3362) [INFO] 
* 05-04:30:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:30:19 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 05-04:30:19 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 05-04:30:19 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 05-04:30:19 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 05-04:30:19 (3372) [INFO]               : zabbix zabbix-non-supported
* 05-04:30:19 (3372) [INFO] Cleaning up list of fastest mirrors
* 05-04:30:19 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 05-04:30:19 (3382) [INFO] 
* 05-04:30:19 (3361) [INFO] Running: /usr/bin/yum check-update
* 05-04:30:19 (3362) [INFO] 
* 05-04:30:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:30:20 (3372) [INFO] Determining fastest mirrors
* 05-04:30:24 (3372) [INFO]  * EA4: 208.100.0.204
* 05-04:30:24 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 05-04:30:24 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 05-04:30:24 (3372) [INFO]  * epel: mirror.dst.ca
* 05-04:30:24 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 05-04:30:48 (3372) [INFO] 
* 05-04:30:48 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 05-04:30:48 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 05-04:30:48 (3382) [INFO] 
* 05-04:30:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 05-04:30:48 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 05-04:30:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 05-04:30:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 05-04:30:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-05_04:30:50_modified_for_AlmaLinux_8.json
* 05-04:30:50 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 05-04:30:50 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 05-04:30:50 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 06-04:27:43 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 06-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 06-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 06-04:27:47 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 06-04:27:47 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 06-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 06-04:28:06 (2925) [INFO] Checking if your system is up to date: 
* 06-04:28:06 (3361) [INFO] Running: /usr/bin/yum clean all
* 06-04:28:06 (3362) [INFO] 
* 06-04:28:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:28:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 06-04:28:06 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 06-04:28:06 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 06-04:28:06 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 06-04:28:06 (3372) [INFO]               : zabbix zabbix-non-supported
* 06-04:28:07 (3372) [INFO] Cleaning up list of fastest mirrors
* 06-04:28:07 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 06-04:28:07 (3382) [INFO] 
* 06-04:28:07 (3361) [INFO] Running: /usr/bin/yum check-update
* 06-04:28:07 (3362) [INFO] 
* 06-04:28:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:28:08 (3372) [INFO] Determining fastest mirrors
* 06-04:28:12 (3372) [INFO]  * EA4: 208.100.0.204
* 06-04:28:12 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 06-04:28:12 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 06-04:28:12 (3372) [INFO]  * epel: mirror.dst.ca
* 06-04:28:12 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 06-04:28:34 (3372) [INFO] 
* 06-04:28:34 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 06-04:28:34 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 06-04:28:34 (3382) [INFO] 
* 06-04:28:34 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 06-04:28:34 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 06-04:28:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 06-04:28:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 06-04:28:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-06_04:28:35_modified_for_AlmaLinux_8.json
* 06-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 06-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 06-04:28:35 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 07-04:30:17 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 07-04:30:25 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 07-04:30:25 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 07-04:30:25 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 07-04:30:25 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 07-04:30:25 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 07-04:30:43 (2925) [INFO] Checking if your system is up to date: 
* 07-04:30:43 (3361) [INFO] Running: /usr/bin/yum clean all
* 07-04:30:43 (3362) [INFO] 
* 07-04:30:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:30:44 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 07-04:30:44 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 07-04:30:44 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 07-04:30:44 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 07-04:30:44 (3372) [INFO]               : zabbix zabbix-non-supported
* 07-04:30:44 (3372) [INFO] Cleaning up list of fastest mirrors
* 07-04:30:44 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 07-04:30:44 (3382) [INFO] 
* 07-04:30:44 (3361) [INFO] Running: /usr/bin/yum check-update
* 07-04:30:44 (3362) [INFO] 
* 07-04:30:45 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:30:45 (3372) [INFO] Determining fastest mirrors
* 07-04:30:51 (3372) [INFO]  * EA4: 208.100.0.204
* 07-04:30:51 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 07-04:30:51 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 07-04:30:51 (3372) [INFO]  * epel: mirror.dst.ca
* 07-04:30:51 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 07-04:31:15 (3372) [INFO] 
* 07-04:31:15 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 07-04:31:15 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 07-04:31:16 (3382) [INFO] 
* 07-04:31:16 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 07-04:31:16 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 07-04:31:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 07-04:31:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 07-04:31:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-07_04:31:19_modified_for_AlmaLinux_8.json
* 07-04:31:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 07-04:31:19 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 07-04:31:19 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 08-04:31:05 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 08-04:31:15 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 08-04:31:15 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 08-04:31:15 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 08-04:31:15 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 08-04:31:15 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 08-04:31:32 (2925) [INFO] Checking if your system is up to date: 
* 08-04:31:32 (3361) [INFO] Running: /usr/bin/yum clean all
* 08-04:31:32 (3362) [INFO] 
* 08-04:31:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:31:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 08-04:31:33 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 08-04:31:33 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 08-04:31:33 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 08-04:31:33 (3372) [INFO]               : zabbix zabbix-non-supported
* 08-04:31:33 (3372) [INFO] Cleaning up list of fastest mirrors
* 08-04:31:33 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 08-04:31:33 (3382) [INFO] 
* 08-04:31:33 (3361) [INFO] Running: /usr/bin/yum check-update
* 08-04:31:33 (3362) [INFO] 
* 08-04:31:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:31:34 (3372) [INFO] Determining fastest mirrors
* 08-04:31:39 (3372) [INFO]  * EA4: 208.100.0.204
* 08-04:31:39 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 08-04:31:39 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 08-04:31:39 (3372) [INFO]  * epel: mirror.dst.ca
* 08-04:31:39 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 08-04:32:06 (3372) [INFO] 
* 08-04:32:06 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 08-04:32:06 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 08-04:32:06 (3382) [INFO] 
* 08-04:32:06 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 08-04:32:06 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 08-04:32:07 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 08-04:32:07 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 08-04:32:08 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-08_04:32:08_modified_for_AlmaLinux_8.json
* 08-04:32:08 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 08-04:32:08 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 08-04:32:08 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 09-04:26:50 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 09-04:26:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 09-04:26:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 09-04:26:53 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 09-04:26:53 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 09-04:26:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 09-04:27:10 (2925) [INFO] Checking if your system is up to date: 
* 09-04:27:10 (3361) [INFO] Running: /usr/bin/yum clean all
* 09-04:27:10 (3362) [INFO] 
* 09-04:27:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 09-04:27:10 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 09-04:27:10 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 09-04:27:10 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 09-04:27:10 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 09-04:27:10 (3372) [INFO]               : zabbix zabbix-non-supported
* 09-04:27:10 (3372) [INFO] Cleaning up list of fastest mirrors
* 09-04:27:10 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 09-04:27:10 (3382) [INFO] 
* 09-04:27:10 (3361) [INFO] Running: /usr/bin/yum check-update
* 09-04:27:10 (3362) [INFO] 
* 09-04:27:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 09-04:27:11 (3372) [INFO] Determining fastest mirrors
* 09-04:27:15 (3372) [INFO]  * EA4: 208.100.0.204
* 09-04:27:15 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 09-04:27:15 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 09-04:27:15 (3372) [INFO]  * epel: epel.mirror.constant.com
* 09-04:27:15 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 09-04:27:40 (3372) [INFO] 
* 09-04:27:40 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 09-04:27:40 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 09-04:27:40 (3382) [INFO] 
* 09-04:27:40 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 09-04:27:40 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 09-04:27:40 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 09-04:27:40 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 09-04:27:41 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-09_04:27:41_modified_for_AlmaLinux_8.json
* 09-04:27:41 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 09-04:27:41 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 09-04:27:41 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 10-04:27:35 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 10-04:27:37 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 10-04:27:37 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 10-04:27:37 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 10-04:27:37 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 10-04:27:37 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 10-04:27:58 (2925) [INFO] Checking if your system is up to date: 
* 10-04:27:58 (3361) [INFO] Running: /usr/bin/yum clean all
* 10-04:27:58 (3362) [INFO] 
* 10-04:27:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:27:59 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 10-04:27:59 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 10-04:27:59 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 10-04:27:59 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 10-04:27:59 (3372) [INFO]               : zabbix zabbix-non-supported
* 10-04:27:59 (3372) [INFO] Cleaning up list of fastest mirrors
* 10-04:27:59 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 10-04:27:59 (3382) [INFO] 
* 10-04:27:59 (3361) [INFO] Running: /usr/bin/yum check-update
* 10-04:27:59 (3362) [INFO] 
* 10-04:28:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:28:00 (3372) [INFO] Determining fastest mirrors
* 10-04:28:06 (3372) [INFO]  * EA4: 208.100.0.204
* 10-04:28:06 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 10-04:28:06 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 10-04:28:06 (3372) [INFO]  * epel: mirror.dst.ca
* 10-04:28:06 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 10-04:28:26 (3372) [INFO] 
* 10-04:28:26 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 10-04:28:26 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 10-04:28:26 (3382) [INFO] 
* 10-04:28:26 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 10-04:28:26 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 10-04:28:26 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 10-04:28:26 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 10-04:28:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-10_04:28:28_modified_for_AlmaLinux_8.json
* 10-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 10-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 10-04:28:28 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 11-04:29:26 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 11-04:29:37 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 11-04:29:37 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 11-04:29:37 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 11-04:29:37 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 11-04:29:37 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 11-04:30:00 (2925) [INFO] Checking if your system is up to date: 
* 11-04:30:00 (3361) [INFO] Running: /usr/bin/yum clean all
* 11-04:30:00 (3362) [INFO] 
* 11-04:30:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:30:01 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 11-04:30:01 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 11-04:30:01 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 11-04:30:01 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 11-04:30:01 (3372) [INFO]               : zabbix zabbix-non-supported
* 11-04:30:01 (3372) [INFO] Cleaning up list of fastest mirrors
* 11-04:30:01 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 11-04:30:01 (3382) [INFO] 
* 11-04:30:01 (3361) [INFO] Running: /usr/bin/yum check-update
* 11-04:30:01 (3362) [INFO] 
* 11-04:30:01 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:30:02 (3372) [INFO] Determining fastest mirrors
* 11-04:30:07 (3372) [INFO]  * EA4: 208.100.0.204
* 11-04:30:07 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 11-04:30:07 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 11-04:30:07 (3372) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 11-04:30:07 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 11-04:30:33 (3372) [INFO] 
* 11-04:30:33 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 11-04:30:33 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 11-04:30:33 (3382) [INFO] 
* 11-04:30:33 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 11-04:30:33 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 11-04:30:33 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 11-04:30:33 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 11-04:30:34 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-11_04:30:34_modified_for_AlmaLinux_8.json
* 11-04:30:34 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 11-04:30:34 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 11-04:30:34 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 12-04:30:56 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 12-04:31:00 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 12-04:31:00 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 12-04:31:00 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 12-04:31:00 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 12-04:31:00 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 12-04:31:22 (2925) [INFO] Checking if your system is up to date: 
* 12-04:31:22 (3361) [INFO] Running: /usr/bin/yum clean all
* 12-04:31:22 (3362) [INFO] 
* 12-04:31:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:31:22 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 12-04:31:22 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 12-04:31:22 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 12-04:31:22 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 12-04:31:22 (3372) [INFO]               : zabbix zabbix-non-supported
* 12-04:31:22 (3372) [INFO] Cleaning up list of fastest mirrors
* 12-04:31:22 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 12-04:31:22 (3382) [INFO] 
* 12-04:31:22 (3361) [INFO] Running: /usr/bin/yum check-update
* 12-04:31:22 (3362) [INFO] 
* 12-04:31:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:31:23 (3372) [INFO] Determining fastest mirrors
* 12-04:31:27 (3372) [INFO]  * EA4: 63.247.64.58
* 12-04:31:27 (3372) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 12-04:31:27 (3372) [INFO]  * cpanel-plugins: 63.247.64.58
* 12-04:31:27 (3372) [INFO]  * epel: mirror.dst.ca
* 12-04:31:27 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 12-04:31:51 (3372) [INFO] 
* 12-04:31:51 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 12-04:31:51 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 12-04:31:51 (3382) [INFO] 
* 12-04:31:51 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 12-04:31:51 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 12-04:31:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 12-04:31:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 12-04:31:52 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-12_04:31:52_modified_for_AlmaLinux_8.json
* 12-04:31:52 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 12-04:31:53 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 12-04:31:53 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 13-04:32:21 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 13-04:32:32 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 13-04:32:32 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 13-04:32:32 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 13-04:32:32 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 13-04:32:32 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 13-04:32:53 (2925) [INFO] Checking if your system is up to date: 
* 13-04:32:53 (3361) [INFO] Running: /usr/bin/yum clean all
* 13-04:32:53 (3362) [INFO] 
* 13-04:32:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:32:54 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 13-04:32:54 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 13-04:32:54 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 13-04:32:54 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 13-04:32:54 (3372) [INFO]               : zabbix zabbix-non-supported
* 13-04:32:54 (3372) [INFO] Cleaning up list of fastest mirrors
* 13-04:32:54 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 13-04:32:54 (3382) [INFO] 
* 13-04:32:54 (3361) [INFO] Running: /usr/bin/yum check-update
* 13-04:32:54 (3362) [INFO] 
* 13-04:32:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:32:55 (3372) [INFO] Determining fastest mirrors
* 13-04:33:00 (3372) [INFO]  * EA4: 208.100.0.204
* 13-04:33:00 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 13-04:33:00 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 13-04:33:00 (3372) [INFO]  * epel: mirror.dst.ca
* 13-04:33:00 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 13-04:33:38 (3372) [INFO] 
* 13-04:33:38 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 13-04:33:38 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 13-04:33:38 (3382) [INFO] 
* 13-04:33:38 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 13-04:33:38 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 13-04:33:38 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 13-04:33:38 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 13-04:33:40 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-13_04:33:40_modified_for_AlmaLinux_8.json
* 13-04:33:40 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 13-04:33:40 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 13-04:33:40 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 14-04:35:07 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 14-04:35:22 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 14-04:35:22 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 14-04:35:22 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 14-04:35:22 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 14-04:35:22 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 14-04:35:42 (2925) [INFO] Checking if your system is up to date: 
* 14-04:35:42 (3361) [INFO] Running: /usr/bin/yum clean all
* 14-04:35:42 (3362) [INFO] 
* 14-04:35:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:35:42 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 14-04:35:42 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 14-04:35:42 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 14-04:35:42 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 14-04:35:42 (3372) [INFO]               : zabbix zabbix-non-supported
* 14-04:35:43 (3372) [INFO] Cleaning up list of fastest mirrors
* 14-04:35:43 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 14-04:35:43 (3382) [INFO] 
* 14-04:35:43 (3361) [INFO] Running: /usr/bin/yum check-update
* 14-04:35:43 (3362) [INFO] 
* 14-04:35:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:35:44 (3372) [INFO] Determining fastest mirrors
* 14-04:35:48 (3372) [INFO]  * EA4: 208.100.0.204
* 14-04:35:48 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 14-04:35:48 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 14-04:35:48 (3372) [INFO]  * epel: mirror.dst.ca
* 14-04:35:48 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 14-04:36:18 (3372) [INFO] 
* 14-04:36:18 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 14-04:36:18 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 14-04:36:18 (3382) [INFO] 
* 14-04:36:18 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 14-04:36:18 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 14-04:36:19 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 14-04:36:19 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 14-04:36:21 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-14_04:36:21_modified_for_AlmaLinux_8.json
* 14-04:36:21 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 14-04:36:21 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 14-04:36:21 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 15-04:33:12 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 15-04:33:25 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 15-04:33:25 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 15-04:33:25 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 15-04:33:25 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 15-04:33:25 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 15-04:33:43 (2925) [INFO] Checking if your system is up to date: 
* 15-04:33:43 (3361) [INFO] Running: /usr/bin/yum clean all
* 15-04:33:43 (3362) [INFO] 
* 15-04:33:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:33:43 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 15-04:33:43 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 15-04:33:43 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 15-04:33:43 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 15-04:33:43 (3372) [INFO]               : zabbix zabbix-non-supported
* 15-04:33:44 (3372) [INFO] Cleaning up list of fastest mirrors
* 15-04:33:44 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 15-04:33:44 (3382) [INFO] 
* 15-04:33:44 (3361) [INFO] Running: /usr/bin/yum check-update
* 15-04:33:44 (3362) [INFO] 
* 15-04:33:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:33:44 (3372) [INFO] Determining fastest mirrors
* 15-04:33:50 (3372) [INFO]  * EA4: 208.100.0.204
* 15-04:33:50 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 15-04:33:50 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 15-04:33:50 (3372) [INFO]  * epel: mirror.dst.ca
* 15-04:33:50 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 15-04:34:20 (3372) [INFO] 
* 15-04:34:20 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 15-04:34:20 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 15-04:34:21 (3382) [INFO] 
* 15-04:34:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 15-04:34:21 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 15-04:34:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 15-04:34:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 15-04:34:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-15_04:34:23_modified_for_AlmaLinux_8.json
* 15-04:34:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 15-04:34:23 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 15-04:34:23 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 16-04:28:11 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 16-04:28:23 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 16-04:28:23 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 16-04:28:23 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 16-04:28:23 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 16-04:28:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 16-04:28:45 (2925) [INFO] Checking if your system is up to date: 
* 16-04:28:45 (3361) [INFO] Running: /usr/bin/yum clean all
* 16-04:28:45 (3362) [INFO] 
* 16-04:28:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:28:46 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 16-04:28:46 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 16-04:28:46 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 16-04:28:46 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 16-04:28:46 (3372) [INFO]               : zabbix zabbix-non-supported
* 16-04:28:46 (3372) [INFO] Cleaning up list of fastest mirrors
* 16-04:28:46 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 16-04:28:46 (3382) [INFO] 
* 16-04:28:46 (3361) [INFO] Running: /usr/bin/yum check-update
* 16-04:28:46 (3362) [INFO] 
* 16-04:28:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:28:47 (3372) [INFO] Determining fastest mirrors
* 16-04:28:51 (3372) [INFO]  * EA4: 208.100.0.204
* 16-04:28:51 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 16-04:28:51 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 16-04:28:51 (3372) [INFO]  * epel: mirror.dst.ca
* 16-04:28:51 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 16-04:29:22 (3372) [INFO] 
* 16-04:29:22 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 16-04:29:22 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 16-04:29:22 (3382) [INFO] 
* 16-04:29:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 16-04:29:22 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 16-04:29:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 16-04:29:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 16-04:29:24 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-16_04:29:24_modified_for_AlmaLinux_8.json
* 16-04:29:24 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 16-04:29:24 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 16-04:29:24 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 17-04:26:58 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 17-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 17-04:26:59 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 17-04:26:59 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 17-04:26:59 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 17-04:26:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 17-04:27:18 (2925) [INFO] Checking if your system is up to date: 
* 17-04:27:18 (3361) [INFO] Running: /usr/bin/yum clean all
* 17-04:27:18 (3362) [INFO] 
* 17-04:27:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:27:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 17-04:27:18 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 17-04:27:18 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 17-04:27:18 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 17-04:27:18 (3372) [INFO]               : zabbix zabbix-non-supported
* 17-04:27:19 (3372) [INFO] Cleaning up list of fastest mirrors
* 17-04:27:19 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 17-04:27:19 (3382) [INFO] 
* 17-04:27:19 (3361) [INFO] Running: /usr/bin/yum check-update
* 17-04:27:19 (3362) [INFO] 
* 17-04:27:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:27:19 (3372) [INFO] Determining fastest mirrors
* 17-04:27:23 (3372) [INFO]  * EA4: 185.125.185.32
* 17-04:27:23 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 17-04:27:23 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 17-04:27:23 (3372) [INFO]  * epel: mirror.dst.ca
* 17-04:27:23 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 17-04:27:48 (3372) [INFO] 
* 17-04:27:48 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 17-04:27:48 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 17-04:27:48 (3382) [INFO] 
* 17-04:27:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 17-04:27:48 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 17-04:27:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 17-04:27:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 17-04:27:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-17_04:27:49_modified_for_AlmaLinux_8.json
* 17-04:27:49 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 17-04:27:49 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 17-04:27:49 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 18-04:28:00 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 18-04:28:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 18-04:28:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 18-04:28:06 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 18-04:28:06 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 18-04:28:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 18-04:28:26 (2925) [INFO] Checking if your system is up to date: 
* 18-04:28:26 (3361) [INFO] Running: /usr/bin/yum clean all
* 18-04:28:26 (3362) [INFO] 
* 18-04:28:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:28:26 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 18-04:28:26 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 18-04:28:26 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 18-04:28:26 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 18-04:28:26 (3372) [INFO]               : zabbix zabbix-non-supported
* 18-04:28:26 (3372) [INFO] Cleaning up list of fastest mirrors
* 18-04:28:26 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 18-04:28:26 (3382) [INFO] 
* 18-04:28:26 (3361) [INFO] Running: /usr/bin/yum check-update
* 18-04:28:26 (3362) [INFO] 
* 18-04:28:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:28:27 (3372) [INFO] Determining fastest mirrors
* 18-04:28:31 (3372) [INFO]  * EA4: 185.125.185.32
* 18-04:28:31 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 18-04:28:31 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 18-04:28:31 (3372) [INFO]  * epel: mirror.dst.ca
* 18-04:28:31 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 18-04:28:58 (3372) [INFO] 
* 18-04:28:58 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 18-04:28:58 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 18-04:28:58 (3382) [INFO] 
* 18-04:28:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 18-04:28:58 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 18-04:28:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 18-04:28:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 18-04:28:59 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-18_04:28:59_modified_for_AlmaLinux_8.json
* 18-04:28:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 18-04:28:59 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 18-04:28:59 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 19-04:32:44 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 19-04:32:48 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 19-04:32:48 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 19-04:32:48 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 19-04:32:48 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 19-04:32:48 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 19-04:33:04 (2925) [INFO] Checking if your system is up to date: 
* 19-04:33:04 (3361) [INFO] Running: /usr/bin/yum clean all
* 19-04:33:04 (3362) [INFO] 
* 19-04:33:04 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:33:05 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 19-04:33:05 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 19-04:33:05 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 19-04:33:05 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 19-04:33:05 (3372) [INFO]               : zabbix zabbix-non-supported
* 19-04:33:05 (3372) [INFO] Cleaning up list of fastest mirrors
* 19-04:33:05 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 19-04:33:05 (3382) [INFO] 
* 19-04:33:05 (3361) [INFO] Running: /usr/bin/yum check-update
* 19-04:33:05 (3362) [INFO] 
* 19-04:33:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:33:05 (3372) [INFO] Determining fastest mirrors
* 19-04:33:09 (3372) [INFO]  * EA4: 185.125.185.32
* 19-04:33:09 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 19-04:33:09 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 19-04:33:09 (3372) [INFO]  * epel: mirror.dst.ca
* 19-04:33:09 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 19-04:33:30 (3372) [INFO] 
* 19-04:33:30 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 19-04:33:30 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 19-04:33:31 (3382) [INFO] 
* 19-04:33:31 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 19-04:33:31 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 19-04:33:31 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 19-04:33:31 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 19-04:33:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-19_04:33:32_modified_for_AlmaLinux_8.json
* 19-04:33:32 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 19-04:33:32 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 19-04:33:32 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 20-04:32:47 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 20-04:32:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 20-04:32:53 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 20-04:32:53 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 20-04:32:53 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 20-04:32:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 20-04:33:28 (2925) [INFO] Checking if your system is up to date: 
* 20-04:33:28 (3361) [INFO] Running: /usr/bin/yum clean all
* 20-04:33:28 (3362) [INFO] 
* 20-04:33:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:33:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 20-04:33:28 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 20-04:33:28 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 20-04:33:28 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 20-04:33:28 (3372) [INFO]               : zabbix zabbix-non-supported
* 20-04:33:29 (3372) [INFO] Cleaning up list of fastest mirrors
* 20-04:33:29 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 20-04:33:29 (3382) [INFO] 
* 20-04:33:29 (3361) [INFO] Running: /usr/bin/yum check-update
* 20-04:33:29 (3362) [INFO] 
* 20-04:33:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:33:29 (3372) [INFO] Determining fastest mirrors
* 20-04:33:35 (3372) [INFO]  * EA4: 185.125.185.32
* 20-04:33:35 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 20-04:33:35 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 20-04:33:35 (3372) [INFO]  * epel: mirror.dst.ca
* 20-04:33:35 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 20-04:34:00 (3372) [INFO] 
* 20-04:34:00 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 20-04:34:00 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 20-04:34:00 (3382) [INFO] 
* 20-04:34:00 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 20-04:34:00 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 20-04:34:00 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 20-04:34:00 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 20-04:34:02 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-20_04:34:02_modified_for_AlmaLinux_8.json
* 20-04:34:02 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 20-04:34:02 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 20-04:34:02 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 21-04:34:12 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 21-04:34:23 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 21-04:34:23 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 21-04:34:23 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 21-04:34:23 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 21-04:34:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 21-04:34:47 (2925) [INFO] Checking if your system is up to date: 
* 21-04:34:47 (3361) [INFO] Running: /usr/bin/yum clean all
* 21-04:34:47 (3362) [INFO] 
* 21-04:34:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:34:47 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 21-04:34:47 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 21-04:34:47 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 21-04:34:47 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 21-04:34:47 (3372) [INFO]               : zabbix zabbix-non-supported
* 21-04:34:48 (3372) [INFO] Cleaning up list of fastest mirrors
* 21-04:34:48 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 21-04:34:48 (3382) [INFO] 
* 21-04:34:48 (3361) [INFO] Running: /usr/bin/yum check-update
* 21-04:34:48 (3362) [INFO] 
* 21-04:34:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:34:48 (3372) [INFO] Determining fastest mirrors
* 21-04:34:53 (3372) [INFO]  * EA4: 185.125.185.32
* 21-04:34:53 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 21-04:34:53 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 21-04:34:53 (3372) [INFO]  * epel: mirror.xenyth.net
* 21-04:34:53 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 21-04:35:21 (3372) [INFO] 
* 21-04:35:21 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 21-04:35:21 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 21-04:35:21 (3382) [INFO] 
* 21-04:35:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 21-04:35:21 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 21-04:35:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 21-04:35:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 21-04:35:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-21_04:35:22_modified_for_AlmaLinux_8.json
* 21-04:35:22 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 21-04:35:22 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 21-04:35:22 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 22-04:29:49 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 22-04:29:52 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 22-04:29:52 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 22-04:29:52 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 22-04:29:52 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 22-04:29:52 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 22-04:30:13 (2925) [INFO] Checking if your system is up to date: 
* 22-04:30:13 (3361) [INFO] Running: /usr/bin/yum clean all
* 22-04:30:13 (3362) [INFO] 
* 22-04:30:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:30:14 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 22-04:30:14 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 22-04:30:14 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 22-04:30:14 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 22-04:30:14 (3372) [INFO]               : zabbix zabbix-non-supported
* 22-04:30:14 (3372) [INFO] Cleaning up list of fastest mirrors
* 22-04:30:14 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 22-04:30:14 (3382) [INFO] 
* 22-04:30:14 (3361) [INFO] Running: /usr/bin/yum check-update
* 22-04:30:14 (3362) [INFO] 
* 22-04:30:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:30:15 (3372) [INFO] Determining fastest mirrors
* 22-04:30:19 (3372) [INFO]  * EA4: 208.100.0.204
* 22-04:30:19 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 22-04:30:19 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 22-04:30:19 (3372) [INFO]  * epel: mirror.dst.ca
* 22-04:30:19 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 22-04:30:45 (3372) [INFO] 
* 22-04:30:45 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 22-04:30:45 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 22-04:30:45 (3382) [INFO] 
* 22-04:30:45 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 22-04:30:45 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 22-04:30:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 22-04:30:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 22-04:30:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-22_04:30:47_modified_for_AlmaLinux_8.json
* 22-04:30:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 22-04:30:47 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 22-04:30:47 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 23-04:27:00 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 23-04:27:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 23-04:27:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 23-04:27:06 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 23-04:27:06 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 23-04:27:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 23-04:27:22 (2925) [INFO] Checking if your system is up to date: 
* 23-04:27:22 (3361) [INFO] Running: /usr/bin/yum clean all
* 23-04:27:22 (3362) [INFO] 
* 23-04:27:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:27:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 23-04:27:23 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 23-04:27:23 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 23-04:27:23 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 23-04:27:23 (3372) [INFO]               : zabbix zabbix-non-supported
* 23-04:27:23 (3372) [INFO] Cleaning up list of fastest mirrors
* 23-04:27:23 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 23-04:27:23 (3382) [INFO] 
* 23-04:27:23 (3361) [INFO] Running: /usr/bin/yum check-update
* 23-04:27:23 (3362) [INFO] 
* 23-04:27:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:27:24 (3372) [INFO] Determining fastest mirrors
* 23-04:27:28 (3372) [INFO]  * EA4: 185.125.185.32
* 23-04:27:28 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 23-04:27:28 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 23-04:27:28 (3372) [INFO]  * epel: mirror.dst.ca
* 23-04:27:28 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 23-04:27:53 (3372) [INFO] 
* 23-04:27:53 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 23-04:27:53 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 23-04:27:53 (3382) [INFO] 
* 23-04:27:53 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 23-04:27:53 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 23-04:27:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 23-04:27:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 23-04:27:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-23_04:27:54_modified_for_AlmaLinux_8.json
* 23-04:27:54 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 23-04:27:54 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 23-04:27:54 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 24-04:26:37 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 24-04:26:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 24-04:26:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 24-04:26:40 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 24-04:26:40 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 24-04:26:40 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 24-04:26:58 (2925) [INFO] Checking if your system is up to date: 
* 24-04:26:58 (3361) [INFO] Running: /usr/bin/yum clean all
* 24-04:26:58 (3362) [INFO] 
* 24-04:26:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:26:59 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 24-04:26:59 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 24-04:26:59 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 24-04:26:59 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 24-04:26:59 (3372) [INFO]               : zabbix zabbix-non-supported
* 24-04:27:00 (3372) [INFO] Cleaning up list of fastest mirrors
* 24-04:27:00 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 24-04:27:00 (3382) [INFO] 
* 24-04:27:00 (3361) [INFO] Running: /usr/bin/yum check-update
* 24-04:27:00 (3362) [INFO] 
* 24-04:27:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:27:00 (3372) [INFO] Determining fastest mirrors
* 24-04:27:05 (3372) [INFO]  * EA4: 185.125.185.32
* 24-04:27:05 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 24-04:27:05 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 24-04:27:05 (3372) [INFO]  * epel: mirror.dst.ca
* 24-04:27:05 (3372) [INFO]  * remi-safe: mirror.usi.edu
* 24-04:27:27 (3372) [INFO] 
* 24-04:27:27 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 24-04:27:27 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 24-04:27:27 (3382) [INFO] 
* 24-04:27:27 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 24-04:27:27 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 24-04:27:27 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 24-04:27:27 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 24-04:27:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-24_04:27:28_modified_for_AlmaLinux_8.json
* 24-04:27:28 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 24-04:27:28 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 24-04:27:28 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 25-04:29:36 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 25-04:29:58 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 25-04:29:58 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 25-04:29:58 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 25-04:29:58 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 25-04:29:58 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 25-04:30:28 (2925) [INFO] Checking if your system is up to date: 
* 25-04:30:28 (3361) [INFO] Running: /usr/bin/yum clean all
* 25-04:30:28 (3362) [INFO] 
* 25-04:30:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:30:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 25-04:30:28 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 25-04:30:28 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 25-04:30:28 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 25-04:30:28 (3372) [INFO]               : zabbix zabbix-non-supported
* 25-04:30:29 (3372) [INFO] Cleaning up list of fastest mirrors
* 25-04:30:29 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 25-04:30:29 (3382) [INFO] 
* 25-04:30:29 (3361) [INFO] Running: /usr/bin/yum check-update
* 25-04:30:29 (3362) [INFO] 
* 25-04:30:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:30:29 (3372) [INFO] Determining fastest mirrors
* 25-04:30:33 (3372) [INFO]  * EA4: 185.125.185.32
* 25-04:30:33 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 25-04:30:33 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 25-04:30:33 (3372) [INFO]  * epel: mirror.dst.ca
* 25-04:30:33 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 25-04:30:58 (3372) [INFO] 
* 25-04:30:58 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 25-04:30:58 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 25-04:30:58 (3382) [INFO] 
* 25-04:30:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 25-04:30:58 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 25-04:30:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 25-04:30:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 25-04:31:02 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-25_04:31:00_modified_for_AlmaLinux_8.json
* 25-04:31:02 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 25-04:31:03 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 25-04:31:03 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 26-04:29:56 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 26-04:30:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 26-04:30:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 26-04:30:03 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 26-04:30:03 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 26-04:30:03 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 26-04:30:26 (2925) [INFO] Checking if your system is up to date: 
* 26-04:30:26 (3361) [INFO] Running: /usr/bin/yum clean all
* 26-04:30:26 (3362) [INFO] 
* 26-04:30:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:30:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 26-04:30:27 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 26-04:30:27 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 26-04:30:27 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 26-04:30:27 (3372) [INFO]               : zabbix zabbix-non-supported
* 26-04:30:27 (3372) [INFO] Cleaning up list of fastest mirrors
* 26-04:30:27 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 26-04:30:27 (3382) [INFO] 
* 26-04:30:27 (3361) [INFO] Running: /usr/bin/yum check-update
* 26-04:30:27 (3362) [INFO] 
* 26-04:30:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:30:27 (3372) [INFO] Determining fastest mirrors
* 26-04:30:32 (3372) [INFO]  * EA4: 185.125.185.32
* 26-04:30:32 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 26-04:30:32 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 26-04:30:32 (3372) [INFO]  * epel: mirror.dst.ca
* 26-04:30:32 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 26-04:30:59 (3372) [INFO] 
* 26-04:30:59 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 26-04:30:59 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 26-04:30:59 (3382) [INFO] 
* 26-04:30:59 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 26-04:30:59 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 26-04:30:59 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 26-04:30:59 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 26-04:31:01 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-26_04:31:01_modified_for_AlmaLinux_8.json
* 26-04:31:01 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 26-04:31:01 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 26-04:31:01 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 27-04:31:51 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 27-04:32:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 27-04:32:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 27-04:32:06 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 27-04:32:06 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 27-04:32:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 27-04:32:31 (2925) [INFO] Checking if your system is up to date: 
* 27-04:32:31 (3361) [INFO] Running: /usr/bin/yum clean all
* 27-04:32:31 (3362) [INFO] 
* 27-04:32:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:32:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 27-04:32:32 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 27-04:32:32 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 27-04:32:32 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 27-04:32:32 (3372) [INFO]               : zabbix zabbix-non-supported
* 27-04:32:32 (3372) [INFO] Cleaning up list of fastest mirrors
* 27-04:32:32 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 27-04:32:32 (3382) [INFO] 
* 27-04:32:32 (3361) [INFO] Running: /usr/bin/yum check-update
* 27-04:32:32 (3362) [INFO] 
* 27-04:32:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:32:33 (3372) [INFO] Determining fastest mirrors
* 27-04:32:37 (3372) [INFO]  * EA4: 185.125.185.32
* 27-04:32:37 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 27-04:32:37 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 27-04:32:37 (3372) [INFO]  * epel: mirror.dst.ca
* 27-04:32:37 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 27-04:33:10 (3372) [INFO] 
* 27-04:33:10 (3372) [INFO] kernel.x86_64                     3.10.0-1160.81.1.el7                   updates
* 27-04:33:10 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 27-04:33:10 (3382) [INFO] 
* 27-04:33:10 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 27-04:33:10 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 27-04:33:10 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 27-04:33:10 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 27-04:33:12 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-27_04:33:12_modified_for_AlmaLinux_8.json
* 27-04:33:12 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 27-04:33:13 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 27-04:33:14 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 28-04:35:28 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 28-04:35:31 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 28-04:35:31 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 28-04:35:31 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 28-04:35:31 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 28-04:35:31 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 28-04:35:52 (2925) [INFO] Checking if your system is up to date: 
* 28-04:35:52 (3361) [INFO] Running: /usr/bin/yum clean all
* 28-04:35:52 (3362) [INFO] 
* 28-04:35:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:35:52 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 28-04:35:52 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 28-04:35:52 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 28-04:35:52 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 28-04:35:52 (3372) [INFO]               : zabbix zabbix-non-supported
* 28-04:35:52 (3372) [INFO] Cleaning up list of fastest mirrors
* 28-04:35:52 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 28-04:35:53 (3382) [INFO] 
* 28-04:35:53 (3361) [INFO] Running: /usr/bin/yum check-update
* 28-04:35:53 (3362) [INFO] 
* 28-04:35:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:35:53 (3372) [INFO] Determining fastest mirrors
* 28-04:35:57 (3372) [INFO]  * EA4: 185.125.185.32
* 28-04:35:57 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 28-04:35:57 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 28-04:35:57 (3372) [INFO]  * epel: mirror.dst.ca
* 28-04:35:57 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 28-04:36:23 (3372) [INFO] 
* 28-04:36:23 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 28-04:36:23 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 28-04:36:23 (3382) [INFO] 
* 28-04:36:23 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 28-04:36:23 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 28-04:36:23 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 28-04:36:23 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 28-04:36:24 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-28_04:36:24_modified_for_AlmaLinux_8.json
* 28-04:36:24 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 28-04:36:24 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 28-04:36:24 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 29-04:30:44 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 29-04:30:52 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 29-04:30:52 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 29-04:30:52 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 29-04:30:52 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 29-04:30:52 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 29-04:31:10 (2925) [INFO] Checking if your system is up to date: 
* 29-04:31:10 (3361) [INFO] Running: /usr/bin/yum clean all
* 29-04:31:10 (3362) [INFO] 
* 29-04:31:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 29-04:31:11 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 29-04:31:11 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 29-04:31:11 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 29-04:31:11 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 29-04:31:11 (3372) [INFO]               : zabbix zabbix-non-supported
* 29-04:31:11 (3372) [INFO] Cleaning up list of fastest mirrors
* 29-04:31:11 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 29-04:31:11 (3382) [INFO] 
* 29-04:31:11 (3361) [INFO] Running: /usr/bin/yum check-update
* 29-04:31:11 (3362) [INFO] 
* 29-04:31:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 29-04:31:12 (3372) [INFO] Determining fastest mirrors
* 29-04:31:16 (3372) [INFO]  * EA4: 208.100.0.204
* 29-04:31:16 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 29-04:31:16 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 29-04:31:16 (3372) [INFO]  * epel: mirror.dst.ca
* 29-04:31:16 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 29-04:31:40 (3372) [INFO] 
* 29-04:31:40 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 29-04:31:40 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 29-04:31:40 (3382) [INFO] 
* 29-04:31:40 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 29-04:31:40 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 29-04:31:40 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 29-04:31:40 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 29-04:31:42 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-29_04:31:42_modified_for_AlmaLinux_8.json
* 29-04:31:42 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 29-04:31:42 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 29-04:31:42 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 30-04:27:32 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 30-04:27:39 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 30-04:27:39 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 30-04:27:39 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 30-04:27:39 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 30-04:27:39 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 30-04:27:55 (2925) [INFO] Checking if your system is up to date: 
* 30-04:27:55 (3361) [INFO] Running: /usr/bin/yum clean all
* 30-04:27:55 (3362) [INFO] 
* 30-04:27:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 30-04:27:56 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 30-04:27:56 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 30-04:27:56 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 30-04:27:56 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 30-04:27:56 (3372) [INFO]               : zabbix zabbix-non-supported
* 30-04:27:56 (3372) [INFO] Cleaning up list of fastest mirrors
* 30-04:27:56 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 30-04:27:56 (3382) [INFO] 
* 30-04:27:56 (3361) [INFO] Running: /usr/bin/yum check-update
* 30-04:27:56 (3362) [INFO] 
* 30-04:27:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 30-04:27:56 (3372) [INFO] Determining fastest mirrors
* 30-04:27:59 (3372) [INFO]  * EA4: 185.125.185.32
* 30-04:27:59 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 30-04:27:59 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 30-04:27:59 (3372) [INFO]  * epel: na.edge.kernel.org
* 30-04:27:59 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 30-04:28:22 (3372) [INFO] 
* 30-04:28:22 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 30-04:28:22 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 30-04:28:22 (3382) [INFO] 
* 30-04:28:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 30-04:28:22 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 30-04:28:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 30-04:28:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 30-04:28:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-30_04:28:23_modified_for_AlmaLinux_8.json
* 30-04:28:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 30-04:28:23 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 30-04:28:23 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 31-04:28:55 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 31-04:29:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 31-04:29:01 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 31-04:29:01 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 31-04:29:01 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 31-04:29:01 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 31-04:29:20 (2925) [INFO] Checking if your system is up to date: 
* 31-04:29:20 (3361) [INFO] Running: /usr/bin/yum clean all
* 31-04:29:20 (3362) [INFO] 
* 31-04:29:20 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 31-04:29:20 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 31-04:29:20 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 31-04:29:20 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 31-04:29:20 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 31-04:29:20 (3372) [INFO]               : zabbix zabbix-non-supported
* 31-04:29:20 (3372) [INFO] Cleaning up list of fastest mirrors
* 31-04:29:20 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 31-04:29:20 (3382) [INFO] 
* 31-04:29:20 (3361) [INFO] Running: /usr/bin/yum check-update
* 31-04:29:20 (3362) [INFO] 
* 31-04:29:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 31-04:29:21 (3372) [INFO] Determining fastest mirrors
* 31-04:29:25 (3372) [INFO]  * EA4: 185.125.185.32
* 31-04:29:25 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 31-04:29:25 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 31-04:29:25 (3372) [INFO]  * epel: mirror.xenyth.net
* 31-04:29:25 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 31-04:29:47 (3372) [INFO] 
* 31-04:29:47 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 31-04:29:47 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 31-04:29:47 (3382) [INFO] 
* 31-04:29:47 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 31-04:29:47 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 31-04:29:47 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 31-04:29:47 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 31-04:29:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-31_04:29:49_modified_for_AlmaLinux_8.json
* 31-04:29:49 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 31-04:29:49 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 31-04:29:49 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 01-04:30:16 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 01-04:30:19 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 01-04:30:19 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 01-04:30:19 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 01-04:30:19 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 01-04:30:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 01-04:30:52 (2925) [INFO] Checking if your system is up to date: 
* 01-04:30:52 (3361) [INFO] Running: /usr/bin/yum clean all
* 01-04:30:52 (3362) [INFO] 
* 01-04:30:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:30:52 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 01-04:30:52 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 01-04:30:52 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 01-04:30:52 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 01-04:30:52 (3372) [INFO]               : zabbix zabbix-non-supported
* 01-04:30:53 (3372) [INFO] Cleaning up list of fastest mirrors
* 01-04:30:53 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 01-04:30:53 (3382) [INFO] 
* 01-04:30:53 (3361) [INFO] Running: /usr/bin/yum check-update
* 01-04:30:53 (3362) [INFO] 
* 01-04:30:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:30:53 (3372) [INFO] Determining fastest mirrors
* 01-04:30:57 (3372) [INFO]  * EA4: 185.125.185.32
* 01-04:30:57 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 01-04:30:57 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 01-04:30:57 (3372) [INFO]  * epel: mirror.dst.ca
* 01-04:30:58 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 01-04:31:21 (3372) [INFO] 
* 01-04:31:21 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 01-04:31:21 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 01-04:31:21 (3382) [INFO] 
* 01-04:31:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 01-04:31:21 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 01-04:31:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 01-04:31:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 01-04:31:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-01_04:31:22_modified_for_AlmaLinux_8.json
* 01-04:31:22 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 01-04:31:22 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 01-04:31:22 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 02-04:30:33 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 02-04:30:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 02-04:30:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 02-04:30:40 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 02-04:30:40 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 02-04:30:40 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 02-04:30:57 (2925) [INFO] Checking if your system is up to date: 
* 02-04:30:57 (3361) [INFO] Running: /usr/bin/yum clean all
* 02-04:30:57 (3362) [INFO] 
* 02-04:30:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:30:58 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 02-04:30:58 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 02-04:30:58 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 02-04:30:58 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 02-04:30:58 (3372) [INFO]               : zabbix zabbix-non-supported
* 02-04:30:58 (3372) [INFO] Cleaning up list of fastest mirrors
* 02-04:30:58 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 02-04:30:58 (3382) [INFO] 
* 02-04:30:58 (3361) [INFO] Running: /usr/bin/yum check-update
* 02-04:30:58 (3362) [INFO] 
* 02-04:30:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:30:59 (3372) [INFO] Determining fastest mirrors
* 02-04:31:02 (3372) [INFO]  * EA4: 185.125.185.32
* 02-04:31:02 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 02-04:31:02 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 02-04:31:02 (3372) [INFO]  * epel: mirror.dst.ca
* 02-04:31:02 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 02-04:31:25 (3372) [INFO] 
* 02-04:31:25 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 02-04:31:25 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 02-04:31:25 (3382) [INFO] 
* 02-04:31:25 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 02-04:31:25 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 02-04:31:25 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 02-04:31:25 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 02-04:31:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-02_04:31:28_modified_for_AlmaLinux_8.json
* 02-04:31:28 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 02-04:31:28 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 02-04:31:28 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 03-04:31:07 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 03-04:31:10 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 03-04:31:10 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 03-04:31:10 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 03-04:31:10 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 03-04:31:10 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 03-04:31:29 (2925) [INFO] Checking if your system is up to date: 
* 03-04:31:29 (3361) [INFO] Running: /usr/bin/yum clean all
* 03-04:31:29 (3362) [INFO] 
* 03-04:31:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:31:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 03-04:31:30 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 03-04:31:30 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 03-04:31:30 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 03-04:31:30 (3372) [INFO]               : zabbix zabbix-non-supported
* 03-04:31:30 (3372) [INFO] Cleaning up list of fastest mirrors
* 03-04:31:30 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 03-04:31:30 (3382) [INFO] 
* 03-04:31:30 (3361) [INFO] Running: /usr/bin/yum check-update
* 03-04:31:30 (3362) [INFO] 
* 03-04:31:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:31:31 (3372) [INFO] Determining fastest mirrors
* 03-04:31:33 (3372) [INFO]  * EA4: 185.125.185.32
* 03-04:31:33 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 03-04:31:33 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 03-04:31:33 (3372) [INFO]  * epel: mirror.dst.ca
* 03-04:31:33 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 03-04:31:57 (3372) [INFO] 
* 03-04:31:57 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 03-04:31:57 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 03-04:31:58 (3382) [INFO] 
* 03-04:31:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 03-04:31:58 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 03-04:31:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 03-04:31:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 03-04:31:59 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-03_04:31:59_modified_for_AlmaLinux_8.json
* 03-04:31:59 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 03-04:31:59 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 03-04:31:59 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 04-04:35:21 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 04-04:35:34 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 04-04:35:34 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 04-04:35:34 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 04-04:35:34 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 04-04:35:34 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 04-04:35:53 (2925) [INFO] Checking if your system is up to date: 
* 04-04:35:53 (3361) [INFO] Running: /usr/bin/yum clean all
* 04-04:35:53 (3362) [INFO] 
* 04-04:35:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:35:53 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 04-04:35:53 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 04-04:35:53 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 04-04:35:53 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 04-04:35:53 (3372) [INFO]               : zabbix zabbix-non-supported
* 04-04:35:54 (3372) [INFO] Cleaning up list of fastest mirrors
* 04-04:35:55 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 04-04:35:55 (3382) [INFO] 
* 04-04:35:55 (3361) [INFO] Running: /usr/bin/yum check-update
* 04-04:35:55 (3362) [INFO] 
* 04-04:35:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:35:55 (3372) [INFO] Determining fastest mirrors
* 04-04:35:58 (3372) [INFO]  * EA4: 185.125.185.32
* 04-04:35:58 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 04-04:35:58 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 04-04:35:58 (3372) [INFO]  * epel: mirror.dst.ca
* 04-04:35:58 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 04-04:36:33 (3372) [INFO] 
* 04-04:36:33 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 04-04:36:33 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 04-04:36:33 (3382) [INFO] 
* 04-04:36:33 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 04-04:36:33 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 04-04:36:33 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 04-04:36:33 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 04-04:36:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-04_04:36:35_modified_for_AlmaLinux_8.json
* 04-04:36:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 04-04:36:35 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 04-04:36:35 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 05-04:38:08 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 05-04:38:20 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 05-04:38:20 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 05-04:38:20 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 05-04:38:20 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 05-04:38:20 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 05-04:38:46 (2925) [INFO] Checking if your system is up to date: 
* 05-04:38:46 (3361) [INFO] Running: /usr/bin/yum clean all
* 05-04:38:46 (3362) [INFO] 
* 05-04:38:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:38:47 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 05-04:38:47 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 05-04:38:47 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 05-04:38:47 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 05-04:38:47 (3372) [INFO]               : zabbix zabbix-non-supported
* 05-04:38:47 (3372) [INFO] Cleaning up list of fastest mirrors
* 05-04:38:47 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 05-04:38:47 (3382) [INFO] 
* 05-04:38:47 (3361) [INFO] Running: /usr/bin/yum check-update
* 05-04:38:47 (3362) [INFO] 
* 05-04:38:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:38:48 (3372) [INFO] Determining fastest mirrors
* 05-04:38:52 (3372) [INFO]  * EA4: 208.100.0.204
* 05-04:38:52 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 05-04:38:52 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 05-04:38:52 (3372) [INFO]  * epel: mirror.dst.ca
* 05-04:38:52 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 05-04:39:31 (3372) [INFO] 
* 05-04:39:31 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 05-04:39:31 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 05-04:39:32 (3382) [INFO] 
* 05-04:39:32 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 05-04:39:32 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 05-04:39:32 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 05-04:39:32 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 05-04:39:34 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-05_04:39:34_modified_for_AlmaLinux_8.json
* 05-04:39:34 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 05-04:39:34 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 05-04:39:34 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 06-04:28:05 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 06-04:28:10 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 06-04:28:10 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 06-04:28:10 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 06-04:28:10 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 06-04:28:10 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 06-04:28:24 (2925) [INFO] Checking if your system is up to date: 
* 06-04:28:24 (3361) [INFO] Running: /usr/bin/yum clean all
* 06-04:28:24 (3362) [INFO] 
* 06-04:28:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:28:24 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 06-04:28:24 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 06-04:28:24 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 06-04:28:24 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 06-04:28:24 (3372) [INFO]               : zabbix zabbix-non-supported
* 06-04:28:24 (3372) [INFO] Cleaning up list of fastest mirrors
* 06-04:28:24 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 06-04:28:24 (3382) [INFO] 
* 06-04:28:24 (3361) [INFO] Running: /usr/bin/yum check-update
* 06-04:28:24 (3362) [INFO] 
* 06-04:28:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:28:25 (3372) [INFO] Determining fastest mirrors
* 06-04:28:28 (3372) [INFO]  * EA4: 208.100.0.204
* 06-04:28:28 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 06-04:28:28 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 06-04:28:28 (3372) [INFO]  * epel: mirror.dst.ca
* 06-04:28:28 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 06-04:28:52 (3372) [INFO] 
* 06-04:28:52 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 06-04:28:52 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 06-04:28:52 (3382) [INFO] 
* 06-04:28:52 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 06-04:28:52 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 06-04:28:52 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 06-04:28:52 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 06-04:28:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-06_04:28:53_modified_for_AlmaLinux_8.json
* 06-04:28:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 06-04:28:53 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 06-04:28:53 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 07-04:31:13 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 07-04:31:17 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 07-04:31:17 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 07-04:31:17 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 07-04:31:17 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 07-04:31:17 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 07-04:31:37 (2925) [INFO] Checking if your system is up to date: 
* 07-04:31:37 (3361) [INFO] Running: /usr/bin/yum clean all
* 07-04:31:37 (3362) [INFO] 
* 07-04:31:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:31:37 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 07-04:31:37 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 07-04:31:37 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 07-04:31:37 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 07-04:31:37 (3372) [INFO]               : zabbix zabbix-non-supported
* 07-04:31:38 (3372) [INFO] Cleaning up list of fastest mirrors
* 07-04:31:38 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 07-04:31:38 (3382) [INFO] 
* 07-04:31:38 (3361) [INFO] Running: /usr/bin/yum check-update
* 07-04:31:38 (3362) [INFO] 
* 07-04:31:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:31:39 (3372) [INFO] Determining fastest mirrors
* 07-04:31:42 (3372) [INFO]  * EA4: 208.100.0.204
* 07-04:31:42 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 07-04:31:42 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 07-04:31:42 (3372) [INFO]  * epel: mirror.dst.ca
* 07-04:31:42 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 07-04:32:06 (3372) [INFO] 
* 07-04:32:06 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 07-04:32:06 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 07-04:32:06 (3382) [INFO] 
* 07-04:32:06 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 07-04:32:06 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 07-04:32:06 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 07-04:32:06 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 07-04:32:07 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-07_04:32:07_modified_for_AlmaLinux_8.json
* 07-04:32:07 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 07-04:32:07 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 07-04:32:07 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 08-04:31:11 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 08-04:31:36 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 08-04:31:36 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 08-04:31:36 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 08-04:31:36 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 08-04:31:36 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 08-04:31:59 (2925) [INFO] Checking if your system is up to date: 
* 08-04:31:59 (3361) [INFO] Running: /usr/bin/yum clean all
* 08-04:31:59 (3362) [INFO] 
* 08-04:31:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:31:59 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 08-04:31:59 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 08-04:31:59 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 08-04:31:59 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 08-04:31:59 (3372) [INFO]               : zabbix zabbix-non-supported
* 08-04:32:00 (3372) [INFO] Cleaning up list of fastest mirrors
* 08-04:32:00 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 08-04:32:00 (3382) [INFO] 
* 08-04:32:00 (3361) [INFO] Running: /usr/bin/yum check-update
* 08-04:32:00 (3362) [INFO] 
* 08-04:32:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:32:01 (3372) [INFO] Determining fastest mirrors
* 08-04:32:05 (3372) [INFO]  * EA4: 185.125.185.32
* 08-04:32:05 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 08-04:32:05 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 08-04:32:05 (3372) [INFO]  * epel: mirror.dst.ca
* 08-04:32:05 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 08-04:32:29 (3372) [INFO] 
* 08-04:32:29 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 08-04:32:29 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 08-04:32:29 (3382) [INFO] 
* 08-04:32:29 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 08-04:32:29 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 08-04:32:29 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 08-04:32:29 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 08-04:32:30 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-08_04:32:30_modified_for_AlmaLinux_8.json
* 08-04:32:30 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 08-04:32:30 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 08-04:32:30 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 09-04:28:56 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 09-04:29:17 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 09-04:29:17 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 09-04:29:17 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 09-04:29:17 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 09-04:29:17 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 09-04:29:36 (2925) [INFO] Checking if your system is up to date: 
* 09-04:29:36 (3361) [INFO] Running: /usr/bin/yum clean all
* 09-04:29:36 (3362) [INFO] 
* 09-04:29:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 09-04:29:37 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 09-04:29:37 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 09-04:29:37 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 09-04:29:37 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 09-04:29:37 (3372) [INFO]               : zabbix zabbix-non-supported
* 09-04:29:38 (3372) [INFO] Cleaning up list of fastest mirrors
* 09-04:29:38 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 09-04:29:38 (3382) [INFO] 
* 09-04:29:38 (3361) [INFO] Running: /usr/bin/yum check-update
* 09-04:29:38 (3362) [INFO] 
* 09-04:29:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 09-04:29:38 (3372) [INFO] Determining fastest mirrors
* 09-04:29:41 (3372) [INFO]  * EA4: 185.125.185.32
* 09-04:29:41 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 09-04:29:41 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 09-04:29:41 (3372) [INFO]  * epel: mirror.dst.ca
* 09-04:29:41 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 09-04:30:09 (3372) [INFO] 
* 09-04:30:09 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 09-04:30:09 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 09-04:30:09 (3382) [INFO] 
* 09-04:30:09 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 09-04:30:09 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 09-04:30:10 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 09-04:30:10 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 09-04:30:12 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-09_04:30:12_modified_for_AlmaLinux_8.json
* 09-04:30:12 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 09-04:30:12 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 09-04:30:12 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 10-04:35:22 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 10-04:35:26 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 10-04:35:26 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 10-04:35:26 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 10-04:35:26 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 10-04:35:26 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 10-04:36:05 (2925) [INFO] Checking if your system is up to date: 
* 10-04:36:05 (3361) [INFO] Running: /usr/bin/yum clean all
* 10-04:36:05 (3362) [INFO] 
* 10-04:36:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:36:05 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 10-04:36:05 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 10-04:36:05 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 10-04:36:05 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 10-04:36:05 (3372) [INFO]               : zabbix zabbix-non-supported
* 10-04:36:06 (3372) [INFO] Cleaning up list of fastest mirrors
* 10-04:36:06 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 10-04:36:06 (3382) [INFO] 
* 10-04:36:06 (3361) [INFO] Running: /usr/bin/yum check-update
* 10-04:36:06 (3362) [INFO] 
* 10-04:36:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 10-04:36:06 (3372) [INFO] Determining fastest mirrors
* 10-04:36:10 (3372) [INFO]  * EA4: 63.247.64.58
* 10-04:36:10 (3372) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 10-04:36:10 (3372) [INFO]  * cpanel-plugins: 63.247.64.58
* 10-04:36:10 (3372) [INFO]  * epel: mirror.dst.ca
* 10-04:36:10 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 10-04:36:36 (3372) [INFO] 
* 10-04:36:36 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 10-04:36:36 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 10-04:36:36 (3382) [INFO] 
* 10-04:36:36 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 10-04:36:36 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 10-04:36:36 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 10-04:36:36 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 10-04:36:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-10_04:36:38_modified_for_AlmaLinux_8.json
* 10-04:36:38 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 10-04:36:38 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 10-04:36:38 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 11-04:44:19 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 11-04:44:43 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 11-04:44:43 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 11-04:44:43 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 11-04:44:43 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 11-04:44:43 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 11-04:45:12 (2925) [INFO] Checking if your system is up to date: 
* 11-04:45:12 (3361) [INFO] Running: /usr/bin/yum clean all
* 11-04:45:12 (3362) [INFO] 
* 11-04:45:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:45:12 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 11-04:45:12 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 11-04:45:12 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 11-04:45:12 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 11-04:45:12 (3372) [INFO]               : zabbix zabbix-non-supported
* 11-04:45:13 (3372) [INFO] Cleaning up list of fastest mirrors
* 11-04:45:13 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 11-04:45:13 (3382) [INFO] 
* 11-04:45:13 (3361) [INFO] Running: /usr/bin/yum check-update
* 11-04:45:13 (3362) [INFO] 
* 11-04:45:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 11-04:45:13 (3372) [INFO] Determining fastest mirrors
* 11-04:45:17 (3372) [INFO]  * EA4: 185.125.185.32
* 11-04:45:17 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 11-04:45:17 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 11-04:45:17 (3372) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 11-04:45:17 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 11-04:45:42 (3372) [INFO] 
* 11-04:45:42 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 11-04:45:42 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 11-04:45:42 (3382) [INFO] 
* 11-04:45:42 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 11-04:45:42 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 11-04:45:42 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 11-04:45:42 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 11-04:45:43 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-11_04:45:43_modified_for_AlmaLinux_8.json
* 11-04:45:43 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 11-04:45:44 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 11-04:45:44 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 12-04:30:49 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 12-04:30:55 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 12-04:30:55 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 12-04:30:55 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 12-04:30:55 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 12-04:30:55 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 12-04:31:08 (2925) [INFO] Checking if your system is up to date: 
* 12-04:31:08 (3361) [INFO] Running: /usr/bin/yum clean all
* 12-04:31:08 (3362) [INFO] 
* 12-04:31:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:31:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 12-04:31:09 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 12-04:31:09 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 12-04:31:09 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 12-04:31:09 (3372) [INFO]               : zabbix zabbix-non-supported
* 12-04:31:09 (3372) [INFO] Cleaning up list of fastest mirrors
* 12-04:31:10 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 12-04:31:10 (3382) [INFO] 
* 12-04:31:10 (3361) [INFO] Running: /usr/bin/yum check-update
* 12-04:31:10 (3362) [INFO] 
* 12-04:31:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 12-04:31:10 (3372) [INFO] Determining fastest mirrors
* 12-04:31:16 (3372) [INFO]  * EA4: 208.100.0.204
* 12-04:31:16 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 12-04:31:16 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 12-04:31:16 (3372) [INFO]  * epel: mirror.dst.ca
* 12-04:31:16 (3372) [INFO]  * remi-safe: mirror.team-cymru.com
* 12-04:31:39 (3372) [INFO] 
* 12-04:31:39 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 12-04:31:39 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 12-04:31:39 (3382) [INFO] 
* 12-04:31:39 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 12-04:31:39 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 12-04:31:39 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 12-04:31:39 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 12-04:31:41 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-12_04:31:41_modified_for_AlmaLinux_8.json
* 12-04:31:41 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 12-04:31:41 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 12-04:31:41 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 13-04:28:49 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 13-04:28:58 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 13-04:28:58 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 13-04:28:58 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 13-04:28:58 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 13-04:28:58 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 13-04:29:34 (2925) [INFO] Checking if your system is up to date: 
* 13-04:29:34 (3361) [INFO] Running: /usr/bin/yum clean all
* 13-04:29:34 (3362) [INFO] 
* 13-04:29:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:29:34 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 13-04:29:34 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 13-04:29:34 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 13-04:29:34 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 13-04:29:34 (3372) [INFO]               : zabbix zabbix-non-supported
* 13-04:29:35 (3372) [INFO] Cleaning up list of fastest mirrors
* 13-04:29:35 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 13-04:29:35 (3382) [INFO] 
* 13-04:29:35 (3361) [INFO] Running: /usr/bin/yum check-update
* 13-04:29:35 (3362) [INFO] 
* 13-04:29:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 13-04:29:35 (3372) [INFO] Determining fastest mirrors
* 13-04:29:38 (3372) [INFO]  * EA4: 185.125.185.32
* 13-04:29:38 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 13-04:29:38 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 13-04:29:38 (3372) [INFO]  * epel: epel.mirror.constant.com
* 13-04:29:38 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 13-04:30:04 (3372) [INFO] 
* 13-04:30:04 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 13-04:30:04 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 13-04:30:05 (3382) [INFO] 
* 13-04:30:05 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 13-04:30:05 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 13-04:30:05 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 13-04:30:05 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 13-04:30:06 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-13_04:30:06_modified_for_AlmaLinux_8.json
* 13-04:30:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 13-04:30:06 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 13-04:30:06 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 14-04:27:25 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 14-04:27:44 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 14-04:27:44 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 14-04:27:44 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 14-04:27:44 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 14-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 14-04:28:06 (2925) [INFO] Checking if your system is up to date: 
* 14-04:28:06 (3361) [INFO] Running: /usr/bin/yum clean all
* 14-04:28:06 (3362) [INFO] 
* 14-04:28:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:28:07 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 14-04:28:07 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 14-04:28:07 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 14-04:28:07 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 14-04:28:07 (3372) [INFO]               : zabbix zabbix-non-supported
* 14-04:28:07 (3372) [INFO] Cleaning up list of fastest mirrors
* 14-04:28:07 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 14-04:28:07 (3382) [INFO] 
* 14-04:28:07 (3361) [INFO] Running: /usr/bin/yum check-update
* 14-04:28:07 (3362) [INFO] 
* 14-04:28:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 14-04:28:07 (3372) [INFO] Determining fastest mirrors
* 14-04:28:11 (3372) [INFO]  * EA4: 185.125.185.32
* 14-04:28:11 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 14-04:28:11 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 14-04:28:11 (3372) [INFO]  * epel: mirror.dst.ca
* 14-04:28:11 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 14-04:28:34 (3372) [INFO] 
* 14-04:28:34 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 14-04:28:34 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 14-04:28:34 (3382) [INFO] 
* 14-04:28:35 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 14-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 14-04:28:35 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 14-04:28:35 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 14-04:28:37 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-14_04:28:37_modified_for_AlmaLinux_8.json
* 14-04:28:37 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 14-04:28:37 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 14-04:28:37 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 15-04:27:12 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 15-04:27:14 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 15-04:27:14 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 15-04:27:14 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 15-04:27:14 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 15-04:27:14 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 15-04:27:31 (2925) [INFO] Checking if your system is up to date: 
* 15-04:27:31 (3361) [INFO] Running: /usr/bin/yum clean all
* 15-04:27:31 (3362) [INFO] 
* 15-04:27:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:27:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 15-04:27:32 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 15-04:27:32 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 15-04:27:32 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 15-04:27:32 (3372) [INFO]               : zabbix zabbix-non-supported
* 15-04:27:32 (3372) [INFO] Cleaning up list of fastest mirrors
* 15-04:27:32 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 15-04:27:32 (3382) [INFO] 
* 15-04:27:32 (3361) [INFO] Running: /usr/bin/yum check-update
* 15-04:27:32 (3362) [INFO] 
* 15-04:27:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 15-04:27:32 (3372) [INFO] Determining fastest mirrors
* 15-04:27:37 (3372) [INFO]  * EA4: 185.125.185.32
* 15-04:27:37 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 15-04:27:37 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 15-04:27:37 (3372) [INFO]  * epel: mirror.dst.ca
* 15-04:27:37 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 15-04:27:58 (3372) [INFO] 
* 15-04:27:58 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 15-04:27:58 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 15-04:27:58 (3382) [INFO] 
* 15-04:27:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 15-04:27:58 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 15-04:27:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 15-04:27:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 15-04:28:00 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-15_04:28:00_modified_for_AlmaLinux_8.json
* 15-04:28:00 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 15-04:28:00 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 15-04:28:00 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 16-04:27:35 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 16-04:27:39 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 16-04:27:39 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 16-04:27:39 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 16-04:27:39 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 16-04:27:39 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 16-04:27:59 (2925) [INFO] Checking if your system is up to date: 
* 16-04:27:59 (3361) [INFO] Running: /usr/bin/yum clean all
* 16-04:27:59 (3362) [INFO] 
* 16-04:27:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:27:59 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 16-04:27:59 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 16-04:27:59 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 16-04:27:59 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 16-04:27:59 (3372) [INFO]               : zabbix zabbix-non-supported
* 16-04:28:00 (3372) [INFO] Cleaning up list of fastest mirrors
* 16-04:28:00 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 16-04:28:00 (3382) [INFO] 
* 16-04:28:00 (3361) [INFO] Running: /usr/bin/yum check-update
* 16-04:28:00 (3362) [INFO] 
* 16-04:28:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 16-04:28:00 (3372) [INFO] Determining fastest mirrors
* 16-04:28:04 (3372) [INFO]  * EA4: 185.125.185.32
* 16-04:28:04 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 16-04:28:04 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 16-04:28:04 (3372) [INFO]  * epel: mirror.dst.ca
* 16-04:28:04 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 16-04:28:26 (3372) [INFO] 
* 16-04:28:26 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 16-04:28:26 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 16-04:28:26 (3382) [INFO] 
* 16-04:28:26 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 16-04:28:26 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 16-04:28:26 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 16-04:28:26 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 16-04:28:27 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-16_04:28:27_modified_for_AlmaLinux_8.json
* 16-04:28:27 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 16-04:28:27 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 16-04:28:27 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 17-04:28:13 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 17-04:28:16 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 17-04:28:16 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 17-04:28:16 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 17-04:28:16 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 17-04:28:16 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 17-04:28:33 (2925) [INFO] Checking if your system is up to date: 
* 17-04:28:33 (3361) [INFO] Running: /usr/bin/yum clean all
* 17-04:28:33 (3362) [INFO] 
* 17-04:28:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:28:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 17-04:28:33 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 17-04:28:33 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 17-04:28:33 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 17-04:28:33 (3372) [INFO]               : zabbix zabbix-non-supported
* 17-04:28:33 (3372) [INFO] Cleaning up list of fastest mirrors
* 17-04:28:33 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 17-04:28:33 (3382) [INFO] 
* 17-04:28:33 (3361) [INFO] Running: /usr/bin/yum check-update
* 17-04:28:33 (3362) [INFO] 
* 17-04:28:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 17-04:28:34 (3372) [INFO] Determining fastest mirrors
* 17-04:28:37 (3372) [INFO]  * EA4: 185.125.185.32
* 17-04:28:37 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 17-04:28:37 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 17-04:28:37 (3372) [INFO]  * epel: mirror.dst.ca
* 17-04:28:37 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 17-04:29:03 (3372) [INFO] 
* 17-04:29:03 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 17-04:29:03 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 17-04:29:03 (3382) [INFO] 
* 17-04:29:03 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 17-04:29:03 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 17-04:29:03 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 17-04:29:03 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 17-04:29:04 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-17_04:29:04_modified_for_AlmaLinux_8.json
* 17-04:29:04 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 17-04:29:04 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 17-04:29:04 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 18-04:27:38 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 18-04:27:41 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 18-04:27:41 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 18-04:27:41 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 18-04:27:41 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 18-04:27:41 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 18-04:27:54 (2925) [INFO] Checking if your system is up to date: 
* 18-04:27:54 (3361) [INFO] Running: /usr/bin/yum clean all
* 18-04:27:54 (3362) [INFO] 
* 18-04:27:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:27:55 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 18-04:27:55 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 18-04:27:55 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 18-04:27:55 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 18-04:27:55 (3372) [INFO]               : zabbix zabbix-non-supported
* 18-04:27:55 (3372) [INFO] Cleaning up list of fastest mirrors
* 18-04:27:55 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 18-04:27:55 (3382) [INFO] 
* 18-04:27:55 (3361) [INFO] Running: /usr/bin/yum check-update
* 18-04:27:55 (3362) [INFO] 
* 18-04:27:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 18-04:27:56 (3372) [INFO] Determining fastest mirrors
* 18-04:27:57 (3372) [INFO]  * EA4: 185.125.185.32
* 18-04:27:57 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 18-04:27:57 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 18-04:27:57 (3372) [INFO]  * epel: mirror.dst.ca
* 18-04:27:57 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 18-04:28:22 (3372) [INFO] 
* 18-04:28:22 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 18-04:28:22 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 18-04:28:22 (3382) [INFO] 
* 18-04:28:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 18-04:28:22 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 18-04:28:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 18-04:28:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 18-04:28:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-18_04:28:23_modified_for_AlmaLinux_8.json
* 18-04:28:23 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 18-04:28:23 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 18-04:28:23 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 19-04:27:48 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 19-04:27:51 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 19-04:27:51 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 19-04:27:51 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 19-04:27:51 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 19-04:27:51 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 19-04:28:05 (2925) [INFO] Checking if your system is up to date: 
* 19-04:28:05 (3361) [INFO] Running: /usr/bin/yum clean all
* 19-04:28:05 (3362) [INFO] 
* 19-04:28:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:28:05 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 19-04:28:05 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 19-04:28:05 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 19-04:28:05 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 19-04:28:05 (3372) [INFO]               : zabbix zabbix-non-supported
* 19-04:28:06 (3372) [INFO] Cleaning up list of fastest mirrors
* 19-04:28:06 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 19-04:28:06 (3382) [INFO] 
* 19-04:28:06 (3361) [INFO] Running: /usr/bin/yum check-update
* 19-04:28:06 (3362) [INFO] 
* 19-04:28:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 19-04:28:07 (3372) [INFO] Determining fastest mirrors
* 19-04:28:10 (3372) [INFO]  * EA4: 185.125.185.32
* 19-04:28:10 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 19-04:28:10 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 19-04:28:10 (3372) [INFO]  * epel: mirror.dst.ca
* 19-04:28:10 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 19-04:28:33 (3372) [INFO] 
* 19-04:28:33 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 19-04:28:33 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 19-04:28:33 (3382) [INFO] 
* 19-04:28:33 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 19-04:28:33 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 19-04:28:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 19-04:28:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 19-04:28:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-19_04:28:35_modified_for_AlmaLinux_8.json
* 19-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 19-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 19-04:28:35 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 20-04:26:38 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 20-04:26:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 20-04:26:40 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 20-04:26:40 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 20-04:26:40 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 20-04:26:40 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 20-04:26:58 (2925) [INFO] Checking if your system is up to date: 
* 20-04:26:58 (3361) [INFO] Running: /usr/bin/yum clean all
* 20-04:26:58 (3362) [INFO] 
* 20-04:26:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:26:58 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 20-04:26:58 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 20-04:26:58 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 20-04:26:58 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 20-04:26:58 (3372) [INFO]               : zabbix zabbix-non-supported
* 20-04:26:58 (3372) [INFO] Cleaning up list of fastest mirrors
* 20-04:26:58 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 20-04:26:58 (3382) [INFO] 
* 20-04:26:58 (3361) [INFO] Running: /usr/bin/yum check-update
* 20-04:26:58 (3362) [INFO] 
* 20-04:26:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 20-04:26:59 (3372) [INFO] Determining fastest mirrors
* 20-04:27:04 (3372) [INFO]  * EA4: 185.125.185.32
* 20-04:27:04 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 20-04:27:04 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 20-04:27:04 (3372) [INFO]  * epel: epel.mirror.constant.com
* 20-04:27:04 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 20-04:27:29 (3372) [INFO] 
* 20-04:27:29 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 20-04:27:29 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 20-04:27:30 (3382) [INFO] 
* 20-04:27:30 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 20-04:27:30 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 20-04:27:30 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 20-04:27:30 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 20-04:27:31 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-20_04:27:31_modified_for_AlmaLinux_8.json
* 20-04:27:31 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 20-04:27:31 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 20-04:27:31 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 21-04:26:51 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 21-04:26:54 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 21-04:26:54 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 21-04:26:54 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 21-04:26:54 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 21-04:26:54 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 21-04:27:13 (2925) [INFO] Checking if your system is up to date: 
* 21-04:27:13 (3361) [INFO] Running: /usr/bin/yum clean all
* 21-04:27:13 (3362) [INFO] 
* 21-04:27:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:27:14 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 21-04:27:14 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 21-04:27:14 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 21-04:27:14 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 21-04:27:14 (3372) [INFO]               : zabbix zabbix-non-supported
* 21-04:27:14 (3372) [INFO] Cleaning up list of fastest mirrors
* 21-04:27:14 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 21-04:27:14 (3382) [INFO] 
* 21-04:27:14 (3361) [INFO] Running: /usr/bin/yum check-update
* 21-04:27:14 (3362) [INFO] 
* 21-04:27:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 21-04:27:15 (3372) [INFO] Determining fastest mirrors
* 21-04:27:19 (3372) [INFO]  * EA4: 185.125.185.32
* 21-04:27:19 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 21-04:27:19 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 21-04:27:19 (3372) [INFO]  * epel: mirror.dst.ca
* 21-04:27:19 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 21-04:27:46 (3372) [INFO] 
* 21-04:27:46 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 21-04:27:46 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 21-04:27:46 (3382) [INFO] 
* 21-04:27:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 21-04:27:46 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 21-04:27:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 21-04:27:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 21-04:27:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-21_04:27:47_modified_for_AlmaLinux_8.json
* 21-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 21-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 21-04:27:47 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 22-04:26:52 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 22-04:26:54 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 22-04:26:54 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 22-04:26:54 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 22-04:26:54 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 22-04:26:54 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 22-04:27:10 (2925) [INFO] Checking if your system is up to date: 
* 22-04:27:10 (3361) [INFO] Running: /usr/bin/yum clean all
* 22-04:27:10 (3362) [INFO] 
* 22-04:27:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:27:10 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 22-04:27:10 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 22-04:27:10 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 22-04:27:10 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 22-04:27:10 (3372) [INFO]               : zabbix zabbix-non-supported
* 22-04:27:10 (3372) [INFO] Cleaning up list of fastest mirrors
* 22-04:27:10 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 22-04:27:10 (3382) [INFO] 
* 22-04:27:10 (3361) [INFO] Running: /usr/bin/yum check-update
* 22-04:27:10 (3362) [INFO] 
* 22-04:27:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 22-04:27:11 (3372) [INFO] Determining fastest mirrors
* 22-04:27:17 (3372) [INFO]  * EA4: 208.100.0.204
* 22-04:27:17 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 22-04:27:17 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 22-04:27:17 (3372) [INFO]  * epel: mirror.dst.ca
* 22-04:27:17 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 22-04:27:43 (3372) [INFO] 
* 22-04:27:43 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 22-04:27:43 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 22-04:27:43 (3382) [INFO] 
* 22-04:27:43 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 22-04:27:43 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 22-04:27:43 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 22-04:27:43 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 22-04:27:44 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-22_04:27:44_modified_for_AlmaLinux_8.json
* 22-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 22-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 22-04:27:44 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 23-04:28:44 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 23-04:28:46 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 23-04:28:46 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 23-04:28:46 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 23-04:28:46 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 23-04:28:46 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 23-04:29:00 (2925) [INFO] Checking if your system is up to date: 
* 23-04:29:00 (3361) [INFO] Running: /usr/bin/yum clean all
* 23-04:29:00 (3362) [INFO] 
* 23-04:29:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:29:00 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 23-04:29:00 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 23-04:29:00 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 23-04:29:00 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 23-04:29:00 (3372) [INFO]               : zabbix zabbix-non-supported
* 23-04:29:00 (3372) [INFO] Cleaning up list of fastest mirrors
* 23-04:29:00 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 23-04:29:00 (3382) [INFO] 
* 23-04:29:00 (3361) [INFO] Running: /usr/bin/yum check-update
* 23-04:29:00 (3362) [INFO] 
* 23-04:29:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 23-04:29:01 (3372) [INFO] Determining fastest mirrors
* 23-04:29:05 (3372) [INFO]  * EA4: 185.125.185.32
* 23-04:29:05 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 23-04:29:05 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 23-04:29:05 (3372) [INFO]  * epel: mirror.dst.ca
* 23-04:29:05 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 23-04:29:31 (3372) [INFO] 
* 23-04:29:31 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 23-04:29:31 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 23-04:29:31 (3382) [INFO] 
* 23-04:29:31 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 23-04:29:31 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 23-04:29:31 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 23-04:29:31 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 23-04:29:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-23_04:29:32_modified_for_AlmaLinux_8.json
* 23-04:29:32 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 23-04:29:32 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 23-04:29:32 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 24-04:27:46 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 24-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 24-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 24-04:27:47 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 24-04:27:47 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 24-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 24-04:28:06 (2925) [INFO] Checking if your system is up to date: 
* 24-04:28:06 (3361) [INFO] Running: /usr/bin/yum clean all
* 24-04:28:06 (3362) [INFO] 
* 24-04:28:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:28:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 24-04:28:06 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 24-04:28:06 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 24-04:28:06 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 24-04:28:06 (3372) [INFO]               : zabbix zabbix-non-supported
* 24-04:28:06 (3372) [INFO] Cleaning up list of fastest mirrors
* 24-04:28:06 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 24-04:28:06 (3382) [INFO] 
* 24-04:28:06 (3361) [INFO] Running: /usr/bin/yum check-update
* 24-04:28:06 (3362) [INFO] 
* 24-04:28:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 24-04:28:07 (3372) [INFO] Determining fastest mirrors
* 24-04:28:10 (3372) [INFO]  * EA4: 185.125.185.32
* 24-04:28:10 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 24-04:28:10 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 24-04:28:10 (3372) [INFO]  * epel: mirror.dst.ca
* 24-04:28:10 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 24-04:28:34 (3372) [INFO] 
* 24-04:28:34 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 24-04:28:34 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 24-04:28:35 (3382) [INFO] 
* 24-04:28:35 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 24-04:28:35 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 24-04:28:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 24-04:28:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 24-04:28:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-24_04:28:38_modified_for_AlmaLinux_8.json
* 24-04:28:38 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 24-04:28:39 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 24-04:28:39 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 25-04:27:45 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 25-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 25-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 25-04:27:47 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 25-04:27:47 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 25-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 25-04:28:01 (2925) [INFO] Checking if your system is up to date: 
* 25-04:28:01 (3361) [INFO] Running: /usr/bin/yum clean all
* 25-04:28:01 (3362) [INFO] 
* 25-04:28:01 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:28:01 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 25-04:28:01 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 25-04:28:01 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 25-04:28:01 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 25-04:28:01 (3372) [INFO]               : zabbix zabbix-non-supported
* 25-04:28:01 (3372) [INFO] Cleaning up list of fastest mirrors
* 25-04:28:01 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 25-04:28:01 (3382) [INFO] 
* 25-04:28:01 (3361) [INFO] Running: /usr/bin/yum check-update
* 25-04:28:01 (3362) [INFO] 
* 25-04:28:02 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 25-04:28:02 (3372) [INFO] Determining fastest mirrors
* 25-04:28:06 (3372) [INFO]  * EA4: 208.100.0.204
* 25-04:28:06 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 25-04:28:06 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 25-04:28:06 (3372) [INFO]  * epel: mirror.dst.ca
* 25-04:28:06 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 25-04:28:27 (3372) [INFO] 
* 25-04:28:27 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 25-04:28:27 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 25-04:28:27 (3382) [INFO] 
* 25-04:28:27 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 25-04:28:27 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 25-04:28:27 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 25-04:28:27 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 25-04:28:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-25_04:28:28_modified_for_AlmaLinux_8.json
* 25-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 25-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 25-04:28:28 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 26-04:27:42 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 26-04:27:44 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 26-04:27:44 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 26-04:27:44 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 26-04:27:44 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 26-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 26-04:27:58 (2925) [INFO] Checking if your system is up to date: 
* 26-04:27:58 (3361) [INFO] Running: /usr/bin/yum clean all
* 26-04:27:58 (3362) [INFO] 
* 26-04:27:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:27:59 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 26-04:27:59 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 26-04:27:59 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 26-04:27:59 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 26-04:27:59 (3372) [INFO]               : zabbix zabbix-non-supported
* 26-04:27:59 (3372) [INFO] Cleaning up list of fastest mirrors
* 26-04:27:59 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 26-04:27:59 (3382) [INFO] 
* 26-04:27:59 (3361) [INFO] Running: /usr/bin/yum check-update
* 26-04:27:59 (3362) [INFO] 
* 26-04:27:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 26-04:28:00 (3372) [INFO] Determining fastest mirrors
* 26-04:28:03 (3372) [INFO]  * EA4: 185.125.185.32
* 26-04:28:03 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 26-04:28:03 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 26-04:28:03 (3372) [INFO]  * epel: mirror.dst.ca
* 26-04:28:03 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 26-04:28:26 (3372) [INFO] 
* 26-04:28:26 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 26-04:28:26 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 26-04:28:26 (3382) [INFO] 
* 26-04:28:26 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 26-04:28:26 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 26-04:28:26 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 26-04:28:26 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 26-04:28:27 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-26_04:28:27_modified_for_AlmaLinux_8.json
* 26-04:28:27 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 26-04:28:28 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 26-04:28:28 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 27-04:26:58 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 27-04:27:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 27-04:27:03 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 27-04:27:03 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 27-04:27:03 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 27-04:27:03 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 27-04:27:18 (2925) [INFO] Checking if your system is up to date: 
* 27-04:27:18 (3361) [INFO] Running: /usr/bin/yum clean all
* 27-04:27:18 (3362) [INFO] 
* 27-04:27:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:27:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 27-04:27:18 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 27-04:27:18 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 27-04:27:18 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 27-04:27:18 (3372) [INFO]               : zabbix zabbix-non-supported
* 27-04:27:18 (3372) [INFO] Cleaning up list of fastest mirrors
* 27-04:27:18 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 27-04:27:18 (3382) [INFO] 
* 27-04:27:18 (3361) [INFO] Running: /usr/bin/yum check-update
* 27-04:27:18 (3362) [INFO] 
* 27-04:27:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 27-04:27:19 (3372) [INFO] Determining fastest mirrors
* 27-04:27:21 (3372) [INFO]  * EA4: 185.125.185.32
* 27-04:27:21 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 27-04:27:21 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 27-04:27:21 (3372) [INFO]  * epel: mirror.xenyth.net
* 27-04:27:21 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 27-04:27:43 (3372) [INFO] 
* 27-04:27:43 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 27-04:27:43 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 27-04:27:44 (3382) [INFO] 
* 27-04:27:44 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 27-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 27-04:27:44 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 27-04:27:44 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 27-04:27:45 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-27_04:27:45_modified_for_AlmaLinux_8.json
* 27-04:27:45 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 27-04:27:45 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 27-04:27:45 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 28-04:27:29 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 28-04:27:32 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 28-04:27:32 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 28-04:27:32 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 28-04:27:32 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 28-04:27:32 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 28-04:27:49 (2925) [INFO] Checking if your system is up to date: 
* 28-04:27:49 (3361) [INFO] Running: /usr/bin/yum clean all
* 28-04:27:49 (3362) [INFO] 
* 28-04:27:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:27:49 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 28-04:27:49 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 28-04:27:49 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 28-04:27:49 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 28-04:27:49 (3372) [INFO]               : zabbix zabbix-non-supported
* 28-04:27:50 (3372) [INFO] Cleaning up list of fastest mirrors
* 28-04:27:50 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 28-04:27:50 (3382) [INFO] 
* 28-04:27:50 (3361) [INFO] Running: /usr/bin/yum check-update
* 28-04:27:50 (3362) [INFO] 
* 28-04:27:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 28-04:27:50 (3372) [INFO] Determining fastest mirrors
* 28-04:27:54 (3372) [INFO]  * EA4: 208.100.0.204
* 28-04:27:54 (3372) [INFO]  * cpanel-addons-production-feed: 208.100.0.204
* 28-04:27:54 (3372) [INFO]  * cpanel-plugins: 208.100.0.204
* 28-04:27:54 (3372) [INFO]  * epel: mirror.dst.ca
* 28-04:27:54 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 28-04:28:16 (3372) [INFO] 
* 28-04:28:16 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 28-04:28:16 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 28-04:28:17 (3382) [INFO] 
* 28-04:28:17 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 28-04:28:17 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 28-04:28:17 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 28-04:28:17 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 28-04:28:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-28_04:28:18_modified_for_AlmaLinux_8.json
* 28-04:28:18 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 28-04:28:18 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 28-04:28:18 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 01-04:26:47 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 01-04:26:49 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 01-04:26:49 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 01-04:26:49 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 01-04:26:49 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 01-04:26:49 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 01-04:27:04 (2925) [INFO] Checking if your system is up to date: 
* 01-04:27:04 (3361) [INFO] Running: /usr/bin/yum clean all
* 01-04:27:04 (3362) [INFO] 
* 01-04:27:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:27:05 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 01-04:27:05 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 01-04:27:05 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 01-04:27:05 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 01-04:27:05 (3372) [INFO]               : zabbix zabbix-non-supported
* 01-04:27:05 (3372) [INFO] Cleaning up list of fastest mirrors
* 01-04:27:05 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 01-04:27:05 (3382) [INFO] 
* 01-04:27:05 (3361) [INFO] Running: /usr/bin/yum check-update
* 01-04:27:05 (3362) [INFO] 
* 01-04:27:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 01-04:27:06 (3372) [INFO] Determining fastest mirrors
* 01-04:27:10 (3372) [INFO]  * EA4: 185.125.185.32
* 01-04:27:10 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 01-04:27:10 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 01-04:27:10 (3372) [INFO]  * epel: mirror.dst.ca
* 01-04:27:10 (3372) [INFO]  * remi-safe: mirror.team-cymru.com
* 01-04:27:31 (3372) [INFO] 
* 01-04:27:31 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 01-04:27:31 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 01-04:27:31 (3382) [INFO] 
* 01-04:27:31 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 01-04:27:31 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 01-04:27:31 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 01-04:27:31 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 01-04:27:33 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-01_04:27:32_modified_for_AlmaLinux_8.json
* 01-04:27:33 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 01-04:27:33 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 01-04:27:33 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 02-04:27:23 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 02-04:27:27 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 02-04:27:27 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 02-04:27:27 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 02-04:27:27 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 02-04:27:27 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 02-04:27:45 (2925) [INFO] Checking if your system is up to date: 
* 02-04:27:45 (3361) [INFO] Running: /usr/bin/yum clean all
* 02-04:27:45 (3362) [INFO] 
* 02-04:27:45 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:27:46 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 02-04:27:46 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 02-04:27:46 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 02-04:27:46 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 02-04:27:46 (3372) [INFO]               : zabbix zabbix-non-supported
* 02-04:27:46 (3372) [INFO] Cleaning up list of fastest mirrors
* 02-04:27:46 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 02-04:27:46 (3382) [INFO] 
* 02-04:27:46 (3361) [INFO] Running: /usr/bin/yum check-update
* 02-04:27:46 (3362) [INFO] 
* 02-04:27:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 02-04:27:46 (3372) [INFO] Determining fastest mirrors
* 02-04:27:49 (3372) [INFO]  * EA4: 185.125.185.32
* 02-04:27:49 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 02-04:27:49 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 02-04:27:49 (3372) [INFO]  * epel: mirror.dst.ca
* 02-04:27:49 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 02-04:28:15 (3372) [INFO] 
* 02-04:28:15 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 02-04:28:15 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 02-04:28:16 (3382) [INFO] 
* 02-04:28:16 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 02-04:28:16 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 02-04:28:16 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 02-04:28:16 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 02-04:28:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-02_04:28:19_modified_for_AlmaLinux_8.json
* 02-04:28:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 02-04:28:19 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 02-04:28:19 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 03-04:26:46 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 03-04:26:48 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 03-04:26:48 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 03-04:26:48 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 03-04:26:48 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 03-04:26:48 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 03-04:27:04 (2925) [INFO] Checking if your system is up to date: 
* 03-04:27:04 (3361) [INFO] Running: /usr/bin/yum clean all
* 03-04:27:04 (3362) [INFO] 
* 03-04:27:04 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:27:05 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 03-04:27:05 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 03-04:27:05 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 03-04:27:05 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 03-04:27:05 (3372) [INFO]               : zabbix zabbix-non-supported
* 03-04:27:05 (3372) [INFO] Cleaning up list of fastest mirrors
* 03-04:27:05 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 03-04:27:05 (3382) [INFO] 
* 03-04:27:05 (3361) [INFO] Running: /usr/bin/yum check-update
* 03-04:27:05 (3362) [INFO] 
* 03-04:27:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 03-04:27:05 (3372) [INFO] Determining fastest mirrors
* 03-04:27:09 (3372) [INFO]  * EA4: 185.125.185.32
* 03-04:27:09 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 03-04:27:09 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 03-04:27:09 (3372) [INFO]  * epel: mirror.dst.ca
* 03-04:27:09 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 03-04:27:33 (3372) [INFO] 
* 03-04:27:33 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 03-04:27:33 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 03-04:27:33 (3382) [INFO] 
* 03-04:27:33 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 03-04:27:33 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 03-04:27:33 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 03-04:27:33 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 03-04:27:34 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-03_04:27:34_modified_for_AlmaLinux_8.json
* 03-04:27:34 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 03-04:27:34 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 03-04:27:34 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 04-04:27:44 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 04-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 04-04:27:47 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 04-04:27:47 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 04-04:27:47 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 04-04:27:47 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 04-04:28:00 (2925) [INFO] Checking if your system is up to date: 
* 04-04:28:00 (3361) [INFO] Running: /usr/bin/yum clean all
* 04-04:28:00 (3362) [INFO] 
* 04-04:28:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:28:00 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 04-04:28:00 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 04-04:28:00 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 04-04:28:00 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 04-04:28:00 (3372) [INFO]               : zabbix zabbix-non-supported
* 04-04:28:01 (3372) [INFO] Cleaning up list of fastest mirrors
* 04-04:28:01 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 04-04:28:01 (3382) [INFO] 
* 04-04:28:01 (3361) [INFO] Running: /usr/bin/yum check-update
* 04-04:28:01 (3362) [INFO] 
* 04-04:28:01 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 04-04:28:01 (3372) [INFO] Determining fastest mirrors
* 04-04:28:05 (3372) [INFO]  * EA4: 185.125.185.32
* 04-04:28:05 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 04-04:28:05 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 04-04:28:05 (3372) [INFO]  * epel: mirror.dst.ca
* 04-04:28:05 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 04-04:28:26 (3372) [INFO] 
* 04-04:28:26 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 04-04:28:26 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 04-04:28:26 (3382) [INFO] 
* 04-04:28:26 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 04-04:28:26 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 04-04:28:26 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 04-04:28:26 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 04-04:28:27 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-04_04:28:27_modified_for_AlmaLinux_8.json
* 04-04:28:27 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 04-04:28:27 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 04-04:28:27 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 05-04:28:06 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 05-04:28:09 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 05-04:28:09 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 05-04:28:09 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 05-04:28:09 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 05-04:28:09 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 05-04:28:22 (2925) [INFO] Checking if your system is up to date: 
* 05-04:28:22 (3361) [INFO] Running: /usr/bin/yum clean all
* 05-04:28:22 (3362) [INFO] 
* 05-04:28:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:28:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 05-04:28:23 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 05-04:28:23 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 05-04:28:23 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 05-04:28:23 (3372) [INFO]               : zabbix zabbix-non-supported
* 05-04:28:23 (3372) [INFO] Cleaning up list of fastest mirrors
* 05-04:28:23 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 05-04:28:23 (3382) [INFO] 
* 05-04:28:23 (3361) [INFO] Running: /usr/bin/yum check-update
* 05-04:28:23 (3362) [INFO] 
* 05-04:28:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 05-04:28:24 (3372) [INFO] Determining fastest mirrors
* 05-04:28:27 (3372) [INFO]  * EA4: 185.125.185.32
* 05-04:28:27 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 05-04:28:27 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 05-04:28:27 (3372) [INFO]  * epel: mirror.dst.ca
* 05-04:28:27 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 05-04:28:49 (3372) [INFO] 
* 05-04:28:49 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 05-04:28:49 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 05-04:28:49 (3382) [INFO] 
* 05-04:28:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 05-04:28:49 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 05-04:28:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 05-04:28:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 05-04:28:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-05_04:28:53_modified_for_AlmaLinux_8.json
* 05-04:28:53 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 05-04:28:53 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 05-04:28:53 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 06-04:26:41 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 06-04:26:43 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 06-04:26:43 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 06-04:26:43 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 06-04:26:43 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 06-04:26:43 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 06-04:26:57 (2925) [INFO] Checking if your system is up to date: 
* 06-04:26:57 (3361) [INFO] Running: /usr/bin/yum clean all
* 06-04:26:57 (3362) [INFO] 
* 06-04:26:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:26:58 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 06-04:26:58 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 06-04:26:58 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 06-04:26:58 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 06-04:26:58 (3372) [INFO]               : zabbix zabbix-non-supported
* 06-04:26:58 (3372) [INFO] Cleaning up list of fastest mirrors
* 06-04:26:58 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 06-04:26:58 (3382) [INFO] 
* 06-04:26:58 (3361) [INFO] Running: /usr/bin/yum check-update
* 06-04:26:58 (3362) [INFO] 
* 06-04:26:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 06-04:26:58 (3372) [INFO] Determining fastest mirrors
* 06-04:27:02 (3372) [INFO]  * EA4: 185.125.185.32
* 06-04:27:02 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 06-04:27:02 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 06-04:27:02 (3372) [INFO]  * epel: epel.mirror.constant.com
* 06-04:27:02 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 06-04:27:24 (3372) [INFO] 
* 06-04:27:24 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 06-04:27:24 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 06-04:27:24 (3382) [INFO] 
* 06-04:27:24 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 06-04:27:24 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 06-04:27:24 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 06-04:27:24 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 06-04:27:26 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-06_04:27:26_modified_for_AlmaLinux_8.json
* 06-04:27:26 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 06-04:27:26 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 06-04:27:26 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 07-04:27:05 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 07-04:27:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 07-04:27:06 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 07-04:27:06 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 07-04:27:06 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 07-04:27:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 07-04:27:17 (2925) [INFO] Checking if your system is up to date: 
* 07-04:27:17 (3361) [INFO] Running: /usr/bin/yum clean all
* 07-04:27:17 (3362) [INFO] 
* 07-04:27:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:27:17 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 07-04:27:17 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 07-04:27:17 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 07-04:27:17 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 07-04:27:17 (3372) [INFO]               : zabbix zabbix-non-supported
* 07-04:27:18 (3372) [INFO] Cleaning up list of fastest mirrors
* 07-04:27:18 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 07-04:27:18 (3382) [INFO] 
* 07-04:27:18 (3361) [INFO] Running: /usr/bin/yum check-update
* 07-04:27:18 (3362) [INFO] 
* 07-04:27:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 07-04:27:18 (3372) [INFO] Determining fastest mirrors
* 07-04:27:23 (3372) [INFO]  * EA4: 185.125.185.32
* 07-04:27:23 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 07-04:27:23 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 07-04:27:23 (3372) [INFO]  * epel: mirror.dst.ca
* 07-04:27:23 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 07-04:27:40 (3372) [INFO] 
* 07-04:27:40 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 07-04:27:40 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 07-04:27:40 (3382) [INFO] 
* 07-04:27:40 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 07-04:27:40 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 07-04:27:40 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 07-04:27:40 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 07-04:27:41 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-07_04:27:41_modified_for_AlmaLinux_8.json
* 07-04:27:41 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 07-04:27:41 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 07-04:27:41 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 08-04:26:53 (2504) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.106.0.18) does not appear to be up to date. Please upgrade cPanel to a most recent version.

* 08-04:26:53 (2504) [WARN] *** Elevation Blocker detected: ***
You have postgresql-server version 9.2 installed.
This is upgraded irreversably to version 10.0 when you switch to almalinux 8
We recommend data backup and removal of all postgresql packages before upgrade to AlmaLinux 8.
To re-install postgresql 9 on AlmaLinux 8, you can run: `dnf -y module enable postgresql:9.6; dnf -y install postgresql-server`


* 08-04:26:56 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 08-04:26:56 (3018) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 08-04:26:56 (3018) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 08-04:26:56 (3029) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 08-04:26:56 (2504) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues


* 08-04:27:12 (2925) [INFO] Checking if your system is up to date: 
* 08-04:27:12 (3361) [INFO] Running: /usr/bin/yum clean all
* 08-04:27:12 (3362) [INFO] 
* 08-04:27:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:27:12 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 08-04:27:12 (3372) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 08-04:27:12 (3372) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 08-04:27:12 (3372) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 08-04:27:12 (3372) [INFO]               : zabbix zabbix-non-supported
* 08-04:27:12 (3372) [INFO] Cleaning up list of fastest mirrors
* 08-04:27:12 (3372) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 08-04:27:12 (3382) [INFO] 
* 08-04:27:12 (3361) [INFO] Running: /usr/bin/yum check-update
* 08-04:27:12 (3362) [INFO] 
* 08-04:27:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 08-04:27:13 (3372) [INFO] Determining fastest mirrors
* 08-04:27:16 (3372) [INFO]  * EA4: 185.125.185.32
* 08-04:27:16 (3372) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 08-04:27:16 (3372) [INFO]  * cpanel-plugins: 185.125.185.32
* 08-04:27:16 (3372) [INFO]  * epel: mirror.dst.ca
* 08-04:27:16 (3372) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 08-04:27:37 (3372) [INFO] 
* 08-04:27:37 (3372) [INFO] kernel.x86_64                     3.10.0-1160.83.1.el7                   updates
* 08-04:27:37 (3372) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 08-04:27:37 (3382) [INFO] 
* 08-04:27:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 08-04:27:37 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date

* 08-04:27:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.
* 08-04:27:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8
* 08-04:27:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-08_04:27:38_modified_for_AlmaLinux_8.json
* 08-04:27:38 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime


* 08-04:27:39 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

wget -O /scripts/elevate-cpanel 
    https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ;
chmod 700 /scripts/elevate-cpanel


Pass the --skip-elevate-version-check flag to skip this check.


* 08-04:27:39 (570) [WARN] Please fix the detected issues before performing the elevation process.

* 2023-03-09 04:35:48 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-09 04:35:48 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-09 04:35:48 (3675) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-09 04:35:48 (3686) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-09 04:35:48 (2749) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-09 04:36:05 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-09 04:36:05 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-09 04:36:05 (4079) [INFO] 
* 2023-03-09 04:36:05 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-09 04:36:05 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-09 04:36:05 (4093) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-09 04:36:05 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-09 04:36:05 (4093) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-09 04:36:05 (4093) [INFO]               : zabbix zabbix-non-supported
* 2023-03-09 04:36:06 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-09 04:36:06 (4093) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-09 04:36:06 (4110) [INFO] 
* 2023-03-09 04:36:06 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-09 04:36:06 (4079) [INFO] 
* 2023-03-09 04:36:32 (4093) [INFO] 
* 2023-03-09 04:36:32 (4093) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-09 04:36:32 (4093) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-09 04:36:33 (4110) [INFO] 
* 2023-03-09 04:36:33 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-09 04:36:33 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-09 04:36:33 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-09 04:36:33 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/H7n6sj3h_b/ea_profile.json
* 2023-03-09 04:36:34 (1694) [INFO] Backed up EA4 profile to /tmp/H7n6sj3h_b/ea_profile.json
* 2023-03-09 04:36:34 (2749) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-09 04:36:34 (2749) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-09 04:36:34 (2858) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-09 04:36:34 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-10 04:26:24 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-10 04:26:24 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-10 04:26:24 (3675) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-10 04:26:24 (3686) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-10 04:26:24 (2749) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-10 04:26:35 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-10 04:26:35 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-10 04:26:35 (4079) [INFO] 
* 2023-03-10 04:26:36 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-10 04:26:36 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-10 04:26:36 (4093) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-10 04:26:36 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-10 04:26:36 (4093) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-10 04:26:36 (4093) [INFO]               : zabbix zabbix-non-supported
* 2023-03-10 04:26:36 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-10 04:26:36 (4093) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-10 04:26:36 (4110) [INFO] 
* 2023-03-10 04:26:36 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-10 04:26:36 (4079) [INFO] 
* 2023-03-10 04:27:02 (4093) [INFO] 
* 2023-03-10 04:27:02 (4093) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-10 04:27:02 (4093) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-10 04:27:02 (4110) [INFO] 
* 2023-03-10 04:27:02 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-10 04:27:02 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-10 04:27:02 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-10 04:27:02 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4GLkdqFJ2g/ea_profile.json
* 2023-03-10 04:27:03 (1694) [INFO] Backed up EA4 profile to /tmp/4GLkdqFJ2g/ea_profile.json
* 2023-03-10 04:27:03 (2749) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-10 04:27:03 (2749) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-10 04:27:03 (2858) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-10 04:27:03 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-11 04:27:12 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-11 04:27:12 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-11 04:27:12 (3675) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-11 04:27:12 (3686) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-11 04:27:12 (2749) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-11 04:27:23 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-11 04:27:23 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-11 04:27:23 (4079) [INFO] 
* 2023-03-11 04:27:23 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-11 04:27:24 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-11 04:27:24 (4093) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-11 04:27:24 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-11 04:27:24 (4093) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-11 04:27:24 (4093) [INFO]               : zabbix zabbix-non-supported
* 2023-03-11 04:27:24 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-11 04:27:24 (4093) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-11 04:27:24 (4110) [INFO] 
* 2023-03-11 04:27:24 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-11 04:27:24 (4079) [INFO] 
* 2023-03-11 04:27:47 (4093) [INFO] 
* 2023-03-11 04:27:47 (4093) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-11 04:27:47 (4093) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-11 04:27:47 (4110) [INFO] 
* 2023-03-11 04:27:47 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-11 04:27:47 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-11 04:27:47 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-11 04:27:47 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cBPmxU3Pt1/ea_profile.json
* 2023-03-11 04:27:48 (1694) [INFO] Backed up EA4 profile to /tmp/cBPmxU3Pt1/ea_profile.json
* 2023-03-11 04:27:48 (2749) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-11 04:27:48 (2749) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-11 04:27:49 (2858) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-11 04:27:49 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-12 04:27:06 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-12 04:27:06 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-12 04:27:06 (3675) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-12 04:27:06 (3686) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-12 04:27:06 (2749) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-12 04:27:17 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-12 04:27:17 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-12 04:27:17 (4079) [INFO] 
* 2023-03-12 04:27:17 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-12 04:27:18 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-12 04:27:18 (4093) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-12 04:27:18 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-12 04:27:18 (4093) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-12 04:27:18 (4093) [INFO]               : zabbix zabbix-non-supported
* 2023-03-12 04:27:18 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-12 04:27:18 (4093) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-12 04:27:18 (4110) [INFO] 
* 2023-03-12 04:27:18 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-12 04:27:18 (4079) [INFO] 
* 2023-03-12 04:27:41 (4093) [INFO] 
* 2023-03-12 04:27:41 (4093) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-12 04:27:41 (4093) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-12 04:27:41 (4110) [INFO] 
* 2023-03-12 04:27:41 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-12 04:27:41 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-12 04:27:41 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-12 04:27:41 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IylUr7gp1P/ea_profile.json
* 2023-03-12 04:27:42 (1694) [INFO] Backed up EA4 profile to /tmp/IylUr7gp1P/ea_profile.json
* 2023-03-12 04:27:42 (2749) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-12 04:27:42 (2749) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-12 04:27:43 (2858) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-12 04:27:43 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-13 04:26:16 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-13 04:26:16 (3675) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-13 04:26:16 (3675) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-13 04:26:16 (3686) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-13 04:26:16 (2749) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-13 04:26:27 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-13 04:26:27 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-13 04:26:27 (4079) [INFO] 
* 2023-03-13 04:26:28 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-13 04:26:28 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-13 04:26:28 (4093) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-13 04:26:28 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-13 04:26:28 (4093) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-13 04:26:28 (4093) [INFO]               : zabbix zabbix-non-supported
* 2023-03-13 04:26:28 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-13 04:26:28 (4093) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-13 04:26:28 (4110) [INFO] 
* 2023-03-13 04:26:28 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-13 04:26:28 (4079) [INFO] 
* 2023-03-13 04:26:52 (4093) [INFO] 
* 2023-03-13 04:26:52 (4093) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-13 04:26:52 (4093) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-13 04:26:52 (4110) [INFO] 
* 2023-03-13 04:26:52 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-13 04:26:52 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-13 04:26:52 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-13 04:26:52 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xSAChbiLT7/ea_profile.json
* 2023-03-13 04:26:53 (1694) [INFO] Backed up EA4 profile to /tmp/xSAChbiLT7/ea_profile.json
* 2023-03-13 04:26:53 (2749) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-13 04:26:54 (2749) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-13 04:26:54 (2858) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-13 04:26:54 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-14 04:26:22 (368) [INFO] Self-update of script version 5 requested.
* 2023-03-14 04:26:22 (373) [INFO] Newer version of script found. Downloading.
* 2023-03-14 04:26:22 (382) [INFO] Script update to version 6 successful.
* 2023-03-14 04:26:25 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-14 04:26:25 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-14 04:26:25 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-14 04:26:25 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-14 04:26:25 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-14 04:26:40 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-14 04:26:40 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-14 04:26:40 (4151) [INFO] 
* 2023-03-14 04:26:40 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-14 04:26:41 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-14 04:26:41 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-14 04:26:41 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-14 04:26:41 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-14 04:26:41 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-14 04:26:41 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-14 04:26:41 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-14 04:26:41 (4182) [INFO] 
* 2023-03-14 04:26:41 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-14 04:26:41 (4151) [INFO] 
* 2023-03-14 04:27:04 (4165) [INFO] 
* 2023-03-14 04:27:04 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-14 04:27:04 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-14 04:27:04 (4182) [INFO] 
* 2023-03-14 04:27:04 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-14 04:27:04 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-14 04:27:04 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-14 04:27:04 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oXYNzGWycG/ea_profile.json
* 2023-03-14 04:27:05 (1765) [INFO] Backed up EA4 profile to /tmp/oXYNzGWycG/ea_profile.json
* 2023-03-14 04:27:05 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-14 04:27:05 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-14 04:27:05 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-14 04:27:05 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-15 04:26:20 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-15 04:26:20 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-15 04:26:20 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-15 04:26:20 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-15 04:26:20 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-15 04:26:32 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-15 04:26:32 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-15 04:26:32 (4151) [INFO] 
* 2023-03-15 04:26:32 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-15 04:26:32 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-15 04:26:32 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-15 04:26:32 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-15 04:26:32 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-15 04:26:32 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-15 04:26:33 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-15 04:26:33 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-15 04:26:33 (4182) [INFO] 
* 2023-03-15 04:26:33 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-15 04:26:33 (4151) [INFO] 
* 2023-03-15 04:26:57 (4165) [INFO] 
* 2023-03-15 04:26:57 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-15 04:26:57 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-15 04:26:57 (4182) [INFO] 
* 2023-03-15 04:26:57 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-15 04:26:57 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-15 04:26:57 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-15 04:26:57 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4SjaJ9m3F2/ea_profile.json
* 2023-03-15 04:26:58 (1765) [INFO] Backed up EA4 profile to /tmp/4SjaJ9m3F2/ea_profile.json
* 2023-03-15 04:26:58 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-15 04:26:58 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-15 04:26:59 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-15 04:26:59 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-16 04:26:29 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-16 04:26:29 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-16 04:26:29 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-16 04:26:29 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-16 04:26:29 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-16 04:26:42 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-16 04:26:42 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-16 04:26:42 (4151) [INFO] 
* 2023-03-16 04:26:42 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-16 04:26:43 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-16 04:26:43 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-16 04:26:43 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-16 04:26:43 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-16 04:26:43 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-16 04:26:43 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-16 04:26:43 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-16 04:26:43 (4182) [INFO] 
* 2023-03-16 04:26:43 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-16 04:26:43 (4151) [INFO] 
* 2023-03-16 04:27:06 (4165) [INFO] 
* 2023-03-16 04:27:06 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-16 04:27:06 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-16 04:27:06 (4182) [INFO] 
* 2023-03-16 04:27:06 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-16 04:27:06 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-16 04:27:06 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-16 04:27:06 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_6yFrrtHfN/ea_profile.json
* 2023-03-16 04:27:07 (1765) [INFO] Backed up EA4 profile to /tmp/_6yFrrtHfN/ea_profile.json
* 2023-03-16 04:27:07 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-16 04:27:07 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-16 04:27:08 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-16 04:27:08 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-17 04:26:25 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-17 04:26:25 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-17 04:26:25 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-17 04:26:25 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-17 04:26:25 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-17 04:26:38 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-17 04:26:38 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-17 04:26:38 (4151) [INFO] 
* 2023-03-17 04:26:39 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-17 04:26:39 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-17 04:26:39 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-17 04:26:39 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-17 04:26:39 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-17 04:26:39 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-17 04:26:39 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-17 04:26:39 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-17 04:26:39 (4182) [INFO] 
* 2023-03-17 04:26:39 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-17 04:26:39 (4151) [INFO] 
* 2023-03-17 04:27:04 (4165) [INFO] 
* 2023-03-17 04:27:04 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-17 04:27:04 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-17 04:27:04 (4182) [INFO] 
* 2023-03-17 04:27:04 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-17 04:27:04 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-17 04:27:04 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-17 04:27:04 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ibZiPmXCND/ea_profile.json
* 2023-03-17 04:27:05 (1765) [INFO] Backed up EA4 profile to /tmp/ibZiPmXCND/ea_profile.json
* 2023-03-17 04:27:05 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-17 04:27:05 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-17 04:27:05 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-17 04:27:05 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-18 04:27:07 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-18 04:27:07 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-18 04:27:07 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-18 04:27:07 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-18 04:27:07 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-18 04:27:18 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-18 04:27:18 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-18 04:27:18 (4151) [INFO] 
* 2023-03-18 04:27:18 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-18 04:27:18 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-18 04:27:18 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-18 04:27:18 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-18 04:27:18 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-18 04:27:18 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-18 04:27:19 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-18 04:27:19 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-18 04:27:19 (4182) [INFO] 
* 2023-03-18 04:27:19 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-18 04:27:19 (4151) [INFO] 
* 2023-03-18 04:27:40 (4165) [INFO] 
* 2023-03-18 04:27:40 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-18 04:27:40 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-18 04:27:41 (4182) [INFO] 
* 2023-03-18 04:27:41 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-18 04:27:41 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-18 04:27:41 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-18 04:27:41 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KkGdeQagEB/ea_profile.json
* 2023-03-18 04:27:41 (1765) [INFO] Backed up EA4 profile to /tmp/KkGdeQagEB/ea_profile.json
* 2023-03-18 04:27:41 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-18 04:27:41 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-18 04:27:42 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-18 04:27:42 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-19 04:27:13 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-19 04:27:13 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-19 04:27:13 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-19 04:27:13 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-19 04:27:13 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-19 04:27:25 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-19 04:27:25 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-19 04:27:25 (4151) [INFO] 
* 2023-03-19 04:27:25 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-19 04:27:25 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-19 04:27:25 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-19 04:27:25 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-19 04:27:25 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-19 04:27:25 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-19 04:27:26 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-19 04:27:26 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-19 04:27:26 (4182) [INFO] 
* 2023-03-19 04:27:26 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-19 04:27:26 (4151) [INFO] 
* 2023-03-19 04:27:48 (4165) [INFO] 
* 2023-03-19 04:27:48 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-19 04:27:48 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-19 04:27:49 (4182) [INFO] 
* 2023-03-19 04:27:49 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-19 04:27:49 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-19 04:27:49 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-19 04:27:49 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/haQC4AeI8D/ea_profile.json
* 2023-03-19 04:27:49 (1765) [INFO] Backed up EA4 profile to /tmp/haQC4AeI8D/ea_profile.json
* 2023-03-19 04:27:49 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-19 04:27:50 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-19 04:27:50 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-19 04:27:50 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-20 04:26:23 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-20 04:26:23 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-20 04:26:23 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-20 04:26:23 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-20 04:26:23 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-20 04:26:39 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-20 04:26:39 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-20 04:26:39 (4151) [INFO] 
* 2023-03-20 04:26:39 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-20 04:26:39 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-20 04:26:39 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-20 04:26:39 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-20 04:26:39 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-20 04:26:39 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-20 04:26:40 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-20 04:26:40 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-20 04:26:40 (4182) [INFO] 
* 2023-03-20 04:26:40 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-20 04:26:40 (4151) [INFO] 
* 2023-03-20 04:27:04 (4165) [INFO] 
* 2023-03-20 04:27:04 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-20 04:27:04 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-20 04:27:04 (4182) [INFO] 
* 2023-03-20 04:27:04 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-20 04:27:04 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-20 04:27:04 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-20 04:27:04 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/85TZCuO7zS/ea_profile.json
* 2023-03-20 04:27:05 (1765) [INFO] Backed up EA4 profile to /tmp/85TZCuO7zS/ea_profile.json
* 2023-03-20 04:27:05 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-20 04:27:05 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-20 04:27:05 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-20 04:27:05 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-21 04:26:21 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-21 04:26:21 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-21 04:26:21 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-21 04:26:21 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-21 04:26:21 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-21 04:26:33 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-21 04:26:33 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-21 04:26:33 (4151) [INFO] 
* 2023-03-21 04:26:33 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-21 04:26:33 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-21 04:26:33 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-21 04:26:33 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-21 04:26:33 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-21 04:26:33 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-21 04:26:34 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-21 04:26:34 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-21 04:26:34 (4182) [INFO] 
* 2023-03-21 04:26:34 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-21 04:26:34 (4151) [INFO] 
* 2023-03-21 04:26:56 (4165) [INFO] 
* 2023-03-21 04:26:56 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-21 04:26:56 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-21 04:26:57 (4182) [INFO] 
* 2023-03-21 04:26:57 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-21 04:26:57 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-21 04:26:57 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-21 04:26:57 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UUU2Zk26re/ea_profile.json
* 2023-03-21 04:26:57 (1765) [INFO] Backed up EA4 profile to /tmp/UUU2Zk26re/ea_profile.json
* 2023-03-21 04:26:57 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-21 04:26:58 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-21 04:26:58 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-21 04:26:58 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-22 04:26:43 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-22 04:26:43 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-22 04:26:43 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-22 04:26:43 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-22 04:26:43 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-22 04:26:55 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-22 04:26:55 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-22 04:26:55 (4151) [INFO] 
* 2023-03-22 04:26:55 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-22 04:26:55 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-22 04:26:55 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-22 04:26:55 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-22 04:26:55 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-22 04:26:55 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-22 04:26:55 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-22 04:26:55 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-22 04:26:56 (4182) [INFO] 
* 2023-03-22 04:26:56 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-22 04:26:56 (4151) [INFO] 
* 2023-03-22 04:27:19 (4165) [INFO] 
* 2023-03-22 04:27:19 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-22 04:27:19 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-22 04:27:19 (4182) [INFO] 
* 2023-03-22 04:27:19 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-22 04:27:19 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-22 04:27:19 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-22 04:27:19 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GGGVHcEIoL/ea_profile.json
* 2023-03-22 04:27:20 (1765) [INFO] Backed up EA4 profile to /tmp/GGGVHcEIoL/ea_profile.json
* 2023-03-22 04:27:20 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-22 04:27:20 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-22 04:27:21 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-22 04:27:21 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-23 04:26:42 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-23 04:26:42 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-23 04:26:42 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-23 04:26:42 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-23 04:26:42 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-23 04:26:55 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-23 04:26:55 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-23 04:26:55 (4151) [INFO] 
* 2023-03-23 04:26:55 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-23 04:26:55 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-23 04:26:55 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-23 04:26:55 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-23 04:26:55 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-23 04:26:55 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-23 04:26:55 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-23 04:26:55 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-23 04:26:55 (4182) [INFO] 
* 2023-03-23 04:26:55 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-23 04:26:55 (4151) [INFO] 
* 2023-03-23 04:27:19 (4165) [INFO] 
* 2023-03-23 04:27:19 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-23 04:27:19 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-23 04:27:19 (4182) [INFO] 
* 2023-03-23 04:27:19 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-23 04:27:19 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-23 04:27:19 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-23 04:27:19 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fK98aWdCjt/ea_profile.json
* 2023-03-23 04:27:20 (1765) [INFO] Backed up EA4 profile to /tmp/fK98aWdCjt/ea_profile.json
* 2023-03-23 04:27:20 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-23 04:27:20 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-23 04:27:20 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-23 04:27:20 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-24 04:26:23 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-24 04:26:23 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-24 04:26:23 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-24 04:26:23 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-24 04:26:23 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-24 04:26:36 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-24 04:26:36 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-24 04:26:36 (4151) [INFO] 
* 2023-03-24 04:26:36 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-24 04:26:36 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-24 04:26:36 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-24 04:26:36 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-24 04:26:36 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-24 04:26:36 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-24 04:26:36 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-24 04:26:36 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-24 04:26:36 (4182) [INFO] 
* 2023-03-24 04:26:36 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-24 04:26:36 (4151) [INFO] 
* 2023-03-24 04:27:00 (4165) [INFO] 
* 2023-03-24 04:27:00 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-24 04:27:00 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-24 04:27:00 (4182) [INFO] 
* 2023-03-24 04:27:00 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-24 04:27:00 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-24 04:27:00 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-24 04:27:00 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hlQZ0MwmA9/ea_profile.json
* 2023-03-24 04:27:01 (1765) [INFO] Backed up EA4 profile to /tmp/hlQZ0MwmA9/ea_profile.json
* 2023-03-24 04:27:01 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-24 04:27:01 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-24 04:27:02 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-24 04:27:02 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-25 04:27:24 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-25 04:27:24 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-25 04:27:24 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-25 04:27:24 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-25 04:27:24 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-25 04:27:37 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-25 04:27:37 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-25 04:27:37 (4151) [INFO] 
* 2023-03-25 04:27:37 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-25 04:27:37 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-25 04:27:37 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-25 04:27:37 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-25 04:27:37 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-25 04:27:37 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-25 04:27:37 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-25 04:27:37 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-25 04:27:37 (4182) [INFO] 
* 2023-03-25 04:27:37 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-25 04:27:37 (4151) [INFO] 
* 2023-03-25 04:28:02 (4165) [INFO] 
* 2023-03-25 04:28:02 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-25 04:28:02 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-25 04:28:02 (4182) [INFO] 
* 2023-03-25 04:28:02 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-25 04:28:02 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-25 04:28:02 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-25 04:28:02 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ot19GfVb8G/ea_profile.json
* 2023-03-25 04:28:03 (1765) [INFO] Backed up EA4 profile to /tmp/Ot19GfVb8G/ea_profile.json
* 2023-03-25 04:28:03 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-25 04:28:03 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-25 04:28:03 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-25 04:28:03 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-26 04:27:26 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-26 04:27:26 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-26 04:27:26 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-26 04:27:26 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-26 04:27:26 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-26 04:27:38 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-03-26 04:27:38 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was
14: HTTPS Error 503 - Service Unavailable
* 2023-03-26 04:27:38 (2820) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-26 04:27:38 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-26 04:27:38 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-26 04:27:38 (4151) [INFO] 
* 2023-03-26 04:27:38 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-26 04:27:38 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-26 04:27:38 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-26 04:27:38 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-26 04:27:38 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-26 04:27:38 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-26 04:27:38 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-26 04:27:38 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-26 04:27:38 (4182) [INFO] 
* 2023-03-26 04:27:38 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-26 04:27:38 (4151) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO]  One of the configured repositories failed (Unknown),
* 2023-03-26 04:27:39 (4165) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-03-26 04:27:39 (4165) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-03-26 04:27:39 (4165) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-03-26 04:27:39 (4165) [INFO]         distribution release than is supported by the repository (and the
* 2023-03-26 04:27:39 (4165) [INFO]         packages for the previous distribution release still work).
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-03-26 04:27:39 (4165) [INFO]             yum --disablerepo=<repoid> ...
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-03-26 04:27:39 (4165) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-03-26 04:27:39 (4165) [INFO]         again or use --enablerepo for temporary usage:
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO]             yum-config-manager --disable <repoid>
* 2023-03-26 04:27:39 (4165) [INFO]         or
* 2023-03-26 04:27:39 (4165) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-03-26 04:27:39 (4165) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-03-26 04:27:39 (4165) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-03-26 04:27:39 (4165) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-03-26 04:27:39 (4165) [INFO]         compromise:
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-03-26 04:27:39 (4165) [INFO] 
* 2023-03-26 04:27:39 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-03-26 04:27:39 (4182) [INFO] 
* 2023-03-26 04:27:39 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-26 04:27:39 (3661) [INFO] Checking /scripts/sysup
* 2023-03-26 04:27:39 (4150) [INFO] Running: /scripts/sysup
* 2023-03-26 04:27:39 (4151) [INFO] 
* 2023-03-26 04:27:40 (4165) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-26 04:27:40 (4165) [INFO]   All Needed Packages are already installed.
* 2023-03-26 04:27:40 (4182) [INFO] 
* 2023-03-26 04:27:40 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-26 04:27:40 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ui1EOCdCyq/ea_profile.json
* 2023-03-26 04:27:42 (2787) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ui1EOCdCyq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1742.
* 2023-03-26 04:27:42 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-27 04:26:20 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-27 04:26:20 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-27 04:26:20 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-27 04:26:20 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-27 04:26:20 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-27 04:26:33 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-27 04:26:33 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-27 04:26:33 (4151) [INFO] 
* 2023-03-27 04:26:33 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-27 04:26:33 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-27 04:26:33 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-27 04:26:33 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-27 04:26:33 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-27 04:26:33 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-27 04:26:33 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-27 04:26:33 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-27 04:26:33 (4182) [INFO] 
* 2023-03-27 04:26:33 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-27 04:26:33 (4151) [INFO] 
* 2023-03-27 04:26:59 (4165) [INFO] 
* 2023-03-27 04:26:59 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-27 04:26:59 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-27 04:26:59 (4182) [INFO] 
* 2023-03-27 04:26:59 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-27 04:26:59 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-27 04:26:59 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-27 04:26:59 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sl6J2_q1ti/ea_profile.json
* 2023-03-27 04:27:00 (1765) [INFO] Backed up EA4 profile to /tmp/sl6J2_q1ti/ea_profile.json
* 2023-03-27 04:27:00 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-27 04:27:00 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-27 04:27:01 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-27 04:27:01 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-28 04:26:19 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-28 04:26:19 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-28 04:26:19 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-28 04:26:19 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-28 04:26:19 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-28 04:26:31 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-28 04:26:31 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-28 04:26:31 (4151) [INFO] 
* 2023-03-28 04:26:31 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-28 04:26:32 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-28 04:26:32 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-28 04:26:32 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-28 04:26:32 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-28 04:26:32 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-28 04:26:32 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-28 04:26:32 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-28 04:26:32 (4182) [INFO] 
* 2023-03-28 04:26:32 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-28 04:26:32 (4151) [INFO] 
* 2023-03-28 04:27:00 (4165) [INFO] 
* 2023-03-28 04:27:00 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-28 04:27:00 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-28 04:27:00 (4182) [INFO] 
* 2023-03-28 04:27:00 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-28 04:27:00 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-28 04:27:00 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-28 04:27:00 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FxSggKCGby/ea_profile.json
* 2023-03-28 04:27:01 (1765) [INFO] Backed up EA4 profile to /tmp/FxSggKCGby/ea_profile.json
* 2023-03-28 04:27:01 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-28 04:27:01 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-28 04:27:02 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-28 04:27:02 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-29 04:26:21 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-29 04:26:21 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-29 04:26:21 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-29 04:26:21 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-29 04:26:21 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-29 04:26:35 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-29 04:26:35 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-29 04:26:35 (4151) [INFO] 
* 2023-03-29 04:26:35 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-29 04:26:35 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-29 04:26:35 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-29 04:26:35 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-29 04:26:35 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-29 04:26:35 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-29 04:26:35 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-29 04:26:35 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-29 04:26:35 (4182) [INFO] 
* 2023-03-29 04:26:35 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-29 04:26:35 (4151) [INFO] 
* 2023-03-29 04:26:58 (4165) [INFO] 
* 2023-03-29 04:26:58 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-29 04:26:58 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-29 04:26:59 (4182) [INFO] 
* 2023-03-29 04:26:59 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-29 04:26:59 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-29 04:26:59 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-29 04:26:59 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/l02tJxih5V/ea_profile.json
* 2023-03-29 04:27:00 (1765) [INFO] Backed up EA4 profile to /tmp/l02tJxih5V/ea_profile.json
* 2023-03-29 04:27:00 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-29 04:27:00 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-29 04:27:00 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-29 04:27:00 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-30 04:27:32 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-30 04:27:32 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-30 04:27:32 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-30 04:27:32 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-30 04:27:32 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-30 04:27:45 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-30 04:27:45 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-30 04:27:45 (4151) [INFO] 
* 2023-03-30 04:27:45 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-30 04:27:45 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-30 04:27:45 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-30 04:27:45 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-30 04:27:45 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-30 04:27:45 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-30 04:27:45 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-30 04:27:45 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-30 04:27:45 (4182) [INFO] 
* 2023-03-30 04:27:45 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-30 04:27:45 (4151) [INFO] 
* 2023-03-30 04:28:10 (4165) [INFO] 
* 2023-03-30 04:28:10 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-30 04:28:10 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-30 04:28:10 (4182) [INFO] 
* 2023-03-30 04:28:10 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-30 04:28:10 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-30 04:28:10 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-30 04:28:10 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DPmZqTNucq/ea_profile.json
* 2023-03-30 04:28:11 (1765) [INFO] Backed up EA4 profile to /tmp/DPmZqTNucq/ea_profile.json
* 2023-03-30 04:28:11 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-30 04:28:11 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-30 04:28:12 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-30 04:28:12 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-31 04:26:19 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-03-31 04:26:19 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-03-31 04:26:19 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-03-31 04:26:19 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-03-31 04:26:19 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-03-31 04:26:31 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-31 04:26:31 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-31 04:26:31 (4151) [INFO] 
* 2023-03-31 04:26:31 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-31 04:26:31 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-31 04:26:31 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-31 04:26:31 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-03-31 04:26:31 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-31 04:26:31 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-03-31 04:26:32 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-31 04:26:32 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-03-31 04:26:32 (4182) [INFO] 
* 2023-03-31 04:26:32 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-31 04:26:32 (4151) [INFO] 
* 2023-03-31 04:26:55 (4165) [INFO] 
* 2023-03-31 04:26:55 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-03-31 04:26:55 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-03-31 04:26:55 (4182) [INFO] 
* 2023-03-31 04:26:55 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-31 04:26:55 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-31 04:26:55 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-31 04:26:55 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7Sk2l6UlA7/ea_profile.json
* 2023-03-31 04:26:56 (1765) [INFO] Backed up EA4 profile to /tmp/7Sk2l6UlA7/ea_profile.json
* 2023-03-31 04:26:56 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-03-31 04:26:56 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-03-31 04:26:56 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-03-31 04:26:56 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-01 04:27:20 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-01 04:27:20 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-01 04:27:20 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-01 04:27:20 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-01 04:27:20 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-01 04:27:31 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-01 04:27:31 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-01 04:27:31 (4151) [INFO] 
* 2023-04-01 04:27:31 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-01 04:27:32 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-01 04:27:32 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-01 04:27:32 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-01 04:27:32 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-01 04:27:32 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-01 04:27:32 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-01 04:27:32 (4165) [INFO] Other repos take up 3.8 M of disk space (use --verbose for details)
* 2023-04-01 04:27:32 (4182) [INFO] 
* 2023-04-01 04:27:32 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-01 04:27:32 (4151) [INFO] 
* 2023-04-01 04:27:55 (4165) [INFO] 
* 2023-04-01 04:27:55 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-01 04:27:55 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-01 04:27:55 (4182) [INFO] 
* 2023-04-01 04:27:55 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-01 04:27:55 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-01 04:27:55 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-01 04:27:55 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/t_jrrXSerf/ea_profile.json
* 2023-04-01 04:27:56 (1765) [INFO] Backed up EA4 profile to /tmp/t_jrrXSerf/ea_profile.json
* 2023-04-01 04:27:56 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-01 04:27:56 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-01 04:27:56 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-01 04:27:56 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-02 04:27:12 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-02 04:27:12 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-02 04:27:12 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-02 04:27:12 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-02 04:27:12 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-02 04:27:25 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-02 04:27:25 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-02 04:27:25 (4151) [INFO] 
* 2023-04-02 04:27:25 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-02 04:27:25 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-02 04:27:25 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-02 04:27:25 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-02 04:27:25 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-02 04:27:25 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-02 04:27:25 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-02 04:27:25 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-02 04:27:25 (4182) [INFO] 
* 2023-04-02 04:27:25 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-02 04:27:25 (4151) [INFO] 
* 2023-04-02 04:27:51 (4165) [INFO] 
* 2023-04-02 04:27:51 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-02 04:27:51 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-02 04:27:51 (4182) [INFO] 
* 2023-04-02 04:27:51 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-02 04:27:51 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-02 04:27:51 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-02 04:27:51 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UfT6KizZxB/ea_profile.json
* 2023-04-02 04:27:52 (1765) [INFO] Backed up EA4 profile to /tmp/UfT6KizZxB/ea_profile.json
* 2023-04-02 04:27:52 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-02 04:27:52 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-02 04:27:52 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-02 04:27:52 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-03 04:26:29 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-03 04:26:29 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-03 04:26:29 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-03 04:26:29 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-03 04:26:29 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-03 04:26:42 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-03 04:26:42 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-03 04:26:42 (4151) [INFO] 
* 2023-04-03 04:26:42 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-03 04:26:42 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-03 04:26:42 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-03 04:26:42 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-03 04:26:42 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-03 04:26:42 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-03 04:26:42 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-03 04:26:42 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-03 04:26:42 (4182) [INFO] 
* 2023-04-03 04:26:42 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-03 04:26:42 (4151) [INFO] 
* 2023-04-03 04:27:10 (4165) [INFO] 
* 2023-04-03 04:27:10 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-03 04:27:10 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-03 04:27:10 (4182) [INFO] 
* 2023-04-03 04:27:10 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-03 04:27:10 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-03 04:27:10 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-03 04:27:10 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sMOe47PTxW/ea_profile.json
* 2023-04-03 04:27:11 (1765) [INFO] Backed up EA4 profile to /tmp/sMOe47PTxW/ea_profile.json
* 2023-04-03 04:27:11 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-03 04:27:11 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-03 04:27:12 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-03 04:27:12 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-04 04:28:05 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-04 04:28:05 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-04 04:28:05 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-04 04:28:05 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-04 04:28:05 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-04 04:28:18 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-04 04:28:18 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-04 04:28:18 (4151) [INFO] 
* 2023-04-04 04:28:18 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-04 04:28:18 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-04 04:28:18 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-04 04:28:18 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-04 04:28:18 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-04 04:28:18 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-04 04:28:18 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-04 04:28:18 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-04 04:28:18 (4182) [INFO] 
* 2023-04-04 04:28:18 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-04 04:28:18 (4151) [INFO] 
* 2023-04-04 04:28:54 (4165) [INFO] 
* 2023-04-04 04:28:54 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-04 04:28:54 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-04 04:28:55 (4182) [INFO] 
* 2023-04-04 04:28:55 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-04 04:28:55 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-04 04:28:55 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-04 04:28:55 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jfiRNV4m0s/ea_profile.json
* 2023-04-04 04:28:55 (1765) [INFO] Backed up EA4 profile to /tmp/jfiRNV4m0s/ea_profile.json
* 2023-04-04 04:28:55 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-04 04:28:56 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-04 04:28:56 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-04 04:28:56 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-05 04:26:32 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-05 04:26:32 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-05 04:26:32 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-05 04:26:32 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-05 04:26:32 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-05 04:26:46 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-05 04:26:46 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-05 04:26:46 (4151) [INFO] 
* 2023-04-05 04:26:46 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-05 04:26:46 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-05 04:26:46 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-05 04:26:46 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-05 04:26:46 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-05 04:26:46 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-05 04:26:46 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-05 04:26:46 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-05 04:26:46 (4182) [INFO] 
* 2023-04-05 04:26:46 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-05 04:26:46 (4151) [INFO] 
* 2023-04-05 04:27:11 (4165) [INFO] 
* 2023-04-05 04:27:11 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-05 04:27:11 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-05 04:27:11 (4182) [INFO] 
* 2023-04-05 04:27:11 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-05 04:27:11 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-05 04:27:11 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-05 04:27:11 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EhZZRLUhRx/ea_profile.json
* 2023-04-05 04:27:12 (1765) [INFO] Backed up EA4 profile to /tmp/EhZZRLUhRx/ea_profile.json
* 2023-04-05 04:27:12 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-05 04:27:12 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-05 04:27:12 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-05 04:27:12 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-06 04:27:51 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-06 04:27:51 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-06 04:27:51 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-06 04:27:51 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-06 04:27:51 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-06 04:28:09 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-06 04:28:09 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-06 04:28:09 (4151) [INFO] 
* 2023-04-06 04:28:09 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-06 04:28:09 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-06 04:28:09 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-06 04:28:09 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-06 04:28:09 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-06 04:28:09 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-06 04:28:09 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-06 04:28:09 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-06 04:28:10 (4182) [INFO] 
* 2023-04-06 04:28:10 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-06 04:28:10 (4151) [INFO] 
* 2023-04-06 04:28:34 (4165) [INFO] 
* 2023-04-06 04:28:34 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-06 04:28:34 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-06 04:28:34 (4182) [INFO] 
* 2023-04-06 04:28:34 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-06 04:28:34 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-06 04:28:34 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-06 04:28:34 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HeF6i96H6M/ea_profile.json
* 2023-04-06 04:28:35 (1765) [INFO] Backed up EA4 profile to /tmp/HeF6i96H6M/ea_profile.json
* 2023-04-06 04:28:35 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-06 04:28:35 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-06 04:28:35 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-06 04:28:35 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-07 04:26:27 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-07 04:26:27 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-07 04:26:27 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-07 04:26:27 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-07 04:26:27 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-07 04:26:42 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-07 04:26:42 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-07 04:26:42 (4151) [INFO] 
* 2023-04-07 04:26:42 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-07 04:26:42 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-07 04:26:42 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-07 04:26:42 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-07 04:26:42 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-07 04:26:42 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-07 04:26:42 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-07 04:26:42 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-07 04:26:42 (4182) [INFO] 
* 2023-04-07 04:26:42 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-07 04:26:42 (4151) [INFO] 
* 2023-04-07 04:27:07 (4165) [INFO] 
* 2023-04-07 04:27:07 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-07 04:27:07 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-07 04:27:07 (4182) [INFO] 
* 2023-04-07 04:27:07 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-07 04:27:07 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-07 04:27:07 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-07 04:27:07 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NZksnKmYMB/ea_profile.json
* 2023-04-07 04:27:08 (1765) [INFO] Backed up EA4 profile to /tmp/NZksnKmYMB/ea_profile.json
* 2023-04-07 04:27:08 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-07 04:27:08 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-07 04:27:08 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-07 04:27:08 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-08 04:27:21 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-08 04:27:21 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-08 04:27:21 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-08 04:27:21 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-08 04:27:21 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-08 04:27:33 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-08 04:27:33 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-08 04:27:33 (4151) [INFO] 
* 2023-04-08 04:27:34 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-08 04:27:34 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-08 04:27:34 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-08 04:27:34 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-08 04:27:34 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-08 04:27:34 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-08 04:27:34 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-08 04:27:34 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-08 04:27:34 (4182) [INFO] 
* 2023-04-08 04:27:34 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-08 04:27:34 (4151) [INFO] 
* 2023-04-08 04:27:59 (4165) [INFO] 
* 2023-04-08 04:27:59 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-08 04:27:59 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-08 04:27:59 (4182) [INFO] 
* 2023-04-08 04:27:59 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-08 04:27:59 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-08 04:27:59 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-08 04:27:59 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pRLwWFRfLL/ea_profile.json
* 2023-04-08 04:28:00 (1765) [INFO] Backed up EA4 profile to /tmp/pRLwWFRfLL/ea_profile.json
* 2023-04-08 04:28:00 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-08 04:28:00 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-08 04:28:00 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-08 04:28:00 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-09 04:27:08 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-09 04:27:08 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-09 04:27:08 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-09 04:27:08 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-09 04:27:08 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-09 04:27:20 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-09 04:27:20 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-09 04:27:20 (4151) [INFO] 
* 2023-04-09 04:27:20 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-09 04:27:20 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-09 04:27:20 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-09 04:27:20 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-09 04:27:20 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-09 04:27:20 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-09 04:27:21 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-09 04:27:21 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-09 04:27:21 (4182) [INFO] 
* 2023-04-09 04:27:21 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-09 04:27:21 (4151) [INFO] 
* 2023-04-09 04:27:44 (4165) [INFO] 
* 2023-04-09 04:27:44 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-09 04:27:44 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-09 04:27:45 (4182) [INFO] 
* 2023-04-09 04:27:45 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-09 04:27:45 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-09 04:27:45 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-09 04:27:45 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XLiZZKHN6e/ea_profile.json
* 2023-04-09 04:27:46 (1765) [INFO] Backed up EA4 profile to /tmp/XLiZZKHN6e/ea_profile.json
* 2023-04-09 04:27:46 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-09 04:27:46 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-09 04:27:46 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-09 04:27:46 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-10 04:26:20 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-10 04:26:20 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-10 04:26:20 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-10 04:26:20 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-10 04:26:20 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-10 04:26:32 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-10 04:26:32 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-10 04:26:32 (4151) [INFO] 
* 2023-04-10 04:26:33 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-10 04:26:33 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-10 04:26:33 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-10 04:26:33 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-10 04:26:33 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-10 04:26:33 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-10 04:26:33 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-10 04:26:33 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-10 04:26:33 (4182) [INFO] 
* 2023-04-10 04:26:33 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-10 04:26:33 (4151) [INFO] 
* 2023-04-10 04:26:58 (4165) [INFO] 
* 2023-04-10 04:26:58 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-10 04:26:58 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-10 04:26:58 (4182) [INFO] 
* 2023-04-10 04:26:58 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-10 04:26:58 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-10 04:26:58 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-10 04:26:58 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YTTpGuNhed/ea_profile.json
* 2023-04-10 04:26:59 (1765) [INFO] Backed up EA4 profile to /tmp/YTTpGuNhed/ea_profile.json
* 2023-04-10 04:26:59 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-10 04:26:59 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-10 04:26:59 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-10 04:26:59 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-11 04:26:23 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-11 04:26:23 (3747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-11 04:26:23 (3747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-11 04:26:23 (3758) [WARN] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo
* 2023-04-11 04:26:23 (2820) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported.
You should disable these repositories and remove packages installed from them
before continuing the update.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-11 04:26:35 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-11 04:26:35 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-11 04:26:35 (4151) [INFO] 
* 2023-04-11 04:26:35 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-11 04:26:35 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-11 04:26:35 (4165) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-11 04:26:35 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-11 04:26:35 (4165) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-11 04:26:35 (4165) [INFO]               : zabbix zabbix-non-supported
* 2023-04-11 04:26:35 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-11 04:26:35 (4165) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-11 04:26:35 (4182) [INFO] 
* 2023-04-11 04:26:35 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-11 04:26:35 (4151) [INFO] 
* 2023-04-11 04:27:01 (4165) [INFO] 
* 2023-04-11 04:27:01 (4165) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-11 04:27:01 (4165) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-11 04:27:01 (4182) [INFO] 
* 2023-04-11 04:27:01 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-11 04:27:01 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-11 04:27:01 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-11 04:27:01 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k_OyGyZ134/ea_profile.json
* 2023-04-11 04:27:02 (1765) [INFO] Backed up EA4 profile to /tmp/k_OyGyZ134/ea_profile.json
* 2023-04-11 04:27:02 (2820) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-11 04:27:02 (2820) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-11 04:27:02 (2929) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-11 04:27:02 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-12 04:26:26 (372) [INFO] Self-update of script version 6 requested.
* 2023-04-12 04:26:26 (377) [INFO] Newer version of script found. Downloading.
* 2023-04-12 04:26:26 (386) [INFO] Script update to version 7 successful.
* 2023-04-12 04:26:29 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-12 04:26:29 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-12 04:26:29 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-12 04:26:29 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-12 04:26:29 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-12 04:26:41 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-12 04:26:41 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-12 04:26:41 (4199) [INFO] 
* 2023-04-12 04:26:41 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-12 04:26:41 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-12 04:26:41 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-12 04:26:41 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-12 04:26:41 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-12 04:26:41 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-12 04:26:42 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-12 04:26:42 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-12 04:26:42 (4230) [INFO] 
* 2023-04-12 04:26:42 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-12 04:26:42 (4199) [INFO] 
* 2023-04-12 04:27:06 (4213) [INFO] 
* 2023-04-12 04:27:06 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-12 04:27:06 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-12 04:27:06 (4230) [INFO] 
* 2023-04-12 04:27:06 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-12 04:27:06 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-12 04:27:06 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-12 04:27:06 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aLD3KFUjdg/ea_profile.json
* 2023-04-12 04:27:07 (1805) [INFO] Backed up EA4 profile to /tmp/aLD3KFUjdg/ea_profile.json
* 2023-04-12 04:27:07 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-12 04:27:07 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-12 04:27:08 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-12 04:27:08 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-13 04:27:52 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-13 04:27:52 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-13 04:27:52 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-13 04:27:52 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-13 04:27:52 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-13 04:28:05 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-13 04:28:05 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-13 04:28:05 (4199) [INFO] 
* 2023-04-13 04:28:05 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-13 04:28:05 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-13 04:28:05 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-13 04:28:05 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-13 04:28:05 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-13 04:28:05 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-13 04:28:05 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-13 04:28:05 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-13 04:28:05 (4230) [INFO] 
* 2023-04-13 04:28:05 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-13 04:28:05 (4199) [INFO] 
* 2023-04-13 04:28:29 (4213) [INFO] 
* 2023-04-13 04:28:29 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-13 04:28:29 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-13 04:28:29 (4230) [INFO] 
* 2023-04-13 04:28:29 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-13 04:28:29 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-13 04:28:29 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-13 04:28:29 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Pg5CnVPWL1/ea_profile.json
* 2023-04-13 04:28:30 (1805) [INFO] Backed up EA4 profile to /tmp/Pg5CnVPWL1/ea_profile.json
* 2023-04-13 04:28:30 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-13 04:28:30 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-13 04:28:31 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-13 04:28:31 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-14 04:26:28 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-14 04:26:28 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-14 04:26:28 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-14 04:26:28 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-14 04:26:28 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-14 04:26:44 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-14 04:26:44 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-14 04:26:44 (4199) [INFO] 
* 2023-04-14 04:26:44 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-14 04:26:44 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-14 04:26:44 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-14 04:26:44 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-14 04:26:44 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-14 04:26:44 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-14 04:26:45 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-14 04:26:45 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-14 04:26:45 (4230) [INFO] 
* 2023-04-14 04:26:45 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-14 04:26:45 (4199) [INFO] 
* 2023-04-14 04:27:11 (4213) [INFO] 
* 2023-04-14 04:27:11 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-14 04:27:11 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-14 04:27:12 (4230) [INFO] 
* 2023-04-14 04:27:12 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-14 04:27:12 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-14 04:27:12 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-14 04:27:12 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_O5uO_D6tv/ea_profile.json
* 2023-04-14 04:27:12 (1805) [INFO] Backed up EA4 profile to /tmp/_O5uO_D6tv/ea_profile.json
* 2023-04-14 04:27:12 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-14 04:27:13 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-14 04:27:13 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-14 04:27:13 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-15 04:27:22 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-15 04:27:22 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-15 04:27:22 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-15 04:27:22 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-15 04:27:22 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-15 04:27:34 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-15 04:27:34 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-15 04:27:34 (4199) [INFO] 
* 2023-04-15 04:27:34 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-15 04:27:34 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-15 04:27:34 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-15 04:27:34 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-15 04:27:34 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-15 04:27:34 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-15 04:27:34 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-15 04:27:34 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-15 04:27:34 (4230) [INFO] 
* 2023-04-15 04:27:34 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-15 04:27:34 (4199) [INFO] 
* 2023-04-15 04:27:59 (4213) [INFO] 
* 2023-04-15 04:27:59 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-15 04:27:59 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-15 04:27:59 (4230) [INFO] 
* 2023-04-15 04:27:59 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-15 04:27:59 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-15 04:27:59 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-15 04:27:59 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vz2W3YrIB9/ea_profile.json
* 2023-04-15 04:28:00 (1805) [INFO] Backed up EA4 profile to /tmp/vz2W3YrIB9/ea_profile.json
* 2023-04-15 04:28:00 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-15 04:28:00 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-15 04:28:00 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-15 04:28:00 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-16 04:27:16 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-16 04:27:16 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-16 04:27:16 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-16 04:27:16 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-16 04:27:16 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-16 04:27:28 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-16 04:27:28 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-16 04:27:28 (4199) [INFO] 
* 2023-04-16 04:27:28 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-16 04:27:28 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-16 04:27:28 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-16 04:27:28 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-16 04:27:28 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-16 04:27:28 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-16 04:27:29 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-16 04:27:29 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-16 04:27:29 (4230) [INFO] 
* 2023-04-16 04:27:29 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-16 04:27:29 (4199) [INFO] 
* 2023-04-16 04:27:52 (4213) [INFO] 
* 2023-04-16 04:27:52 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-16 04:27:52 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-16 04:27:53 (4230) [INFO] 
* 2023-04-16 04:27:53 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-16 04:27:53 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-16 04:27:53 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-16 04:27:53 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FEZZ0yfz2Q/ea_profile.json
* 2023-04-16 04:27:53 (1805) [INFO] Backed up EA4 profile to /tmp/FEZZ0yfz2Q/ea_profile.json
* 2023-04-16 04:27:53 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-16 04:27:54 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-16 04:27:54 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-16 04:27:54 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-17 04:26:20 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-17 04:26:20 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-17 04:26:20 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-17 04:26:20 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-17 04:26:20 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-17 04:26:33 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-17 04:26:33 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-17 04:26:33 (4199) [INFO] 
* 2023-04-17 04:26:33 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-17 04:26:33 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-17 04:26:33 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-17 04:26:33 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-17 04:26:33 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-17 04:26:33 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-17 04:26:34 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-17 04:26:34 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-17 04:26:34 (4230) [INFO] 
* 2023-04-17 04:26:34 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-17 04:26:34 (4199) [INFO] 
* 2023-04-17 04:26:59 (4213) [INFO] 
* 2023-04-17 04:26:59 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-17 04:26:59 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-17 04:27:00 (4230) [INFO] 
* 2023-04-17 04:27:00 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-17 04:27:00 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-17 04:27:00 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-17 04:27:00 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gABZVRKb6X/ea_profile.json
* 2023-04-17 04:27:01 (1805) [INFO] Backed up EA4 profile to /tmp/gABZVRKb6X/ea_profile.json
* 2023-04-17 04:27:01 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-17 04:27:01 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-17 04:27:01 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-17 04:27:01 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-18 04:26:28 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-18 04:26:28 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-18 04:26:28 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-18 04:26:28 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-18 04:26:28 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-18 04:26:41 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-18 04:26:41 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-18 04:26:41 (4199) [INFO] 
* 2023-04-18 04:26:41 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-18 04:26:41 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-18 04:26:41 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-18 04:26:41 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-18 04:26:41 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-18 04:26:41 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-18 04:26:42 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-18 04:26:42 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-18 04:26:42 (4230) [INFO] 
* 2023-04-18 04:26:42 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-18 04:26:42 (4199) [INFO] 
* 2023-04-18 04:27:09 (4213) [INFO] 
* 2023-04-18 04:27:09 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-18 04:27:09 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-18 04:27:09 (4230) [INFO] 
* 2023-04-18 04:27:09 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-18 04:27:09 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-18 04:27:09 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-18 04:27:09 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4dRECHMvzq/ea_profile.json
* 2023-04-18 04:27:10 (1805) [INFO] Backed up EA4 profile to /tmp/4dRECHMvzq/ea_profile.json
* 2023-04-18 04:27:10 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-18 04:27:10 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-18 04:27:11 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-18 04:27:11 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-19 04:26:18 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-19 04:26:18 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-19 04:26:18 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-19 04:26:18 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-19 04:26:18 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-19 04:26:31 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-19 04:26:31 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-19 04:26:31 (4199) [INFO] 
* 2023-04-19 04:26:31 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-19 04:26:32 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-19 04:26:32 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-19 04:26:32 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-19 04:26:32 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-19 04:26:32 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-19 04:26:32 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-19 04:26:32 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-19 04:26:32 (4230) [INFO] 
* 2023-04-19 04:26:32 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-19 04:26:32 (4199) [INFO] 
* 2023-04-19 04:26:56 (4213) [INFO] 
* 2023-04-19 04:26:56 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-19 04:26:56 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-19 04:26:56 (4230) [INFO] 
* 2023-04-19 04:26:56 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-19 04:26:56 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-19 04:26:56 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-19 04:26:56 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wfRzxTbdGx/ea_profile.json
* 2023-04-19 04:26:57 (1805) [INFO] Backed up EA4 profile to /tmp/wfRzxTbdGx/ea_profile.json
* 2023-04-19 04:26:57 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-19 04:26:57 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-19 04:26:57 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-19 04:26:57 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-20 04:27:49 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-20 04:27:49 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-20 04:27:49 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-20 04:27:49 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-20 04:27:49 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-20 04:28:05 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-20 04:28:05 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-20 04:28:05 (4199) [INFO] 
* 2023-04-20 04:28:05 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-20 04:28:05 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-20 04:28:05 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-20 04:28:05 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-20 04:28:05 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-20 04:28:05 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-20 04:28:06 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-20 04:28:06 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-20 04:28:06 (4230) [INFO] 
* 2023-04-20 04:28:06 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-20 04:28:06 (4199) [INFO] 
* 2023-04-20 04:28:31 (4213) [INFO] 
* 2023-04-20 04:28:31 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-20 04:28:31 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-20 04:28:31 (4230) [INFO] 
* 2023-04-20 04:28:31 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-20 04:28:31 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-20 04:28:31 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-20 04:28:31 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IMgdeuKn1A/ea_profile.json
* 2023-04-20 04:28:32 (1805) [INFO] Backed up EA4 profile to /tmp/IMgdeuKn1A/ea_profile.json
* 2023-04-20 04:28:32 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-20 04:28:32 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-20 04:28:32 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-20 04:28:32 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-21 04:27:00 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-21 04:27:00 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-21 04:27:00 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-21 04:27:00 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-21 04:27:00 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-21 04:27:13 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-21 04:27:13 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-21 04:27:13 (4199) [INFO] 
* 2023-04-21 04:27:13 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-21 04:27:13 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-21 04:27:13 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-21 04:27:13 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-21 04:27:13 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-21 04:27:13 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-21 04:27:14 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-21 04:27:14 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-21 04:27:14 (4230) [INFO] 
* 2023-04-21 04:27:14 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-21 04:27:14 (4199) [INFO] 
* 2023-04-21 04:27:42 (4213) [INFO] 
* 2023-04-21 04:27:42 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-21 04:27:42 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-21 04:27:42 (4230) [INFO] 
* 2023-04-21 04:27:42 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-21 04:27:42 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-21 04:27:42 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-21 04:27:42 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7rtwS0PAxw/ea_profile.json
* 2023-04-21 04:27:43 (1805) [INFO] Backed up EA4 profile to /tmp/7rtwS0PAxw/ea_profile.json
* 2023-04-21 04:27:43 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-21 04:27:43 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-21 04:27:43 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-21 04:27:43 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-22 04:27:22 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-22 04:27:22 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-22 04:27:22 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-22 04:27:22 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-22 04:27:22 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-22 04:27:38 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-22 04:27:38 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-22 04:27:38 (4199) [INFO] 
* 2023-04-22 04:27:38 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-22 04:27:38 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-22 04:27:38 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-22 04:27:38 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-22 04:27:38 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-22 04:27:38 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-22 04:27:39 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-22 04:27:39 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-22 04:27:39 (4230) [INFO] 
* 2023-04-22 04:27:39 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-22 04:27:39 (4199) [INFO] 
* 2023-04-22 04:28:04 (4213) [INFO] 
* 2023-04-22 04:28:04 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-22 04:28:04 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-22 04:28:04 (4230) [INFO] 
* 2023-04-22 04:28:04 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-22 04:28:04 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-22 04:28:04 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-22 04:28:04 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rKukr4SA7o/ea_profile.json
* 2023-04-22 04:28:05 (1805) [INFO] Backed up EA4 profile to /tmp/rKukr4SA7o/ea_profile.json
* 2023-04-22 04:28:05 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-22 04:28:05 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-22 04:28:06 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-22 04:28:06 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-23 04:27:10 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-23 04:27:10 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-23 04:27:10 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-23 04:27:10 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-23 04:27:10 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-23 04:27:23 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-23 04:27:23 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-23 04:27:23 (4199) [INFO] 
* 2023-04-23 04:27:23 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-23 04:27:23 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-23 04:27:23 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-23 04:27:23 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-23 04:27:23 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-23 04:27:23 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-23 04:27:23 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-23 04:27:23 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-23 04:27:23 (4230) [INFO] 
* 2023-04-23 04:27:23 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-23 04:27:23 (4199) [INFO] 
* 2023-04-23 04:27:48 (4213) [INFO] 
* 2023-04-23 04:27:48 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-23 04:27:48 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-23 04:27:48 (4230) [INFO] 
* 2023-04-23 04:27:48 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-23 04:27:48 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-23 04:27:48 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-23 04:27:48 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KVZmRa1ghu/ea_profile.json
* 2023-04-23 04:27:49 (1805) [INFO] Backed up EA4 profile to /tmp/KVZmRa1ghu/ea_profile.json
* 2023-04-23 04:27:49 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-23 04:27:49 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-23 04:27:50 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-23 04:27:50 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-24 04:26:32 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-24 04:26:32 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-24 04:26:32 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-24 04:26:32 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-24 04:26:32 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-24 04:26:48 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-24 04:26:48 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-24 04:26:48 (4199) [INFO] 
* 2023-04-24 04:26:48 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-24 04:26:48 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-24 04:26:48 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-24 04:26:48 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-24 04:26:48 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-24 04:26:48 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-24 04:26:48 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-24 04:26:48 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-24 04:26:48 (4230) [INFO] 
* 2023-04-24 04:26:48 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-24 04:26:48 (4199) [INFO] 
* 2023-04-24 04:27:14 (4213) [INFO] 
* 2023-04-24 04:27:14 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-24 04:27:14 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-24 04:27:15 (4230) [INFO] 
* 2023-04-24 04:27:15 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-24 04:27:15 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-24 04:27:15 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-24 04:27:15 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eYXk4MpBNG/ea_profile.json
* 2023-04-24 04:27:15 (1805) [INFO] Backed up EA4 profile to /tmp/eYXk4MpBNG/ea_profile.json
* 2023-04-24 04:27:15 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-24 04:27:16 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-24 04:27:16 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-24 04:27:16 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-25 04:26:23 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-25 04:26:23 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-25 04:26:23 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-25 04:26:23 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-25 04:26:23 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-25 04:26:36 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-25 04:26:36 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-25 04:26:36 (4199) [INFO] 
* 2023-04-25 04:26:37 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-25 04:26:37 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-25 04:26:37 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-25 04:26:37 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-25 04:26:37 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-25 04:26:37 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-25 04:26:37 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-25 04:26:37 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-25 04:26:37 (4230) [INFO] 
* 2023-04-25 04:26:37 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-25 04:26:37 (4199) [INFO] 
* 2023-04-25 04:27:03 (4213) [INFO] 
* 2023-04-25 04:27:03 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-25 04:27:03 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-25 04:27:03 (4230) [INFO] 
* 2023-04-25 04:27:03 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-25 04:27:03 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-25 04:27:03 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-25 04:27:03 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pSxySzwvcx/ea_profile.json
* 2023-04-25 04:27:04 (1805) [INFO] Backed up EA4 profile to /tmp/pSxySzwvcx/ea_profile.json
* 2023-04-25 04:27:04 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-25 04:27:04 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-25 04:27:04 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-25 04:27:04 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-26 04:26:24 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-26 04:26:24 (3796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-26 04:26:24 (3796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-26 04:26:24 (3807) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-26 04:26:24 (2856) [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.

Consider reporting this limitation to https://github.com/cpanel/elevate/issues

* 2023-04-26 04:26:36 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-26 04:26:36 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-26 04:26:36 (4199) [INFO] 
* 2023-04-26 04:26:36 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-26 04:26:37 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-26 04:26:37 (4213) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-26 04:26:37 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-26 04:26:37 (4213) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-26 04:26:37 (4213) [INFO]               : zabbix zabbix-non-supported
* 2023-04-26 04:26:37 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-26 04:26:37 (4213) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-26 04:26:37 (4230) [INFO] 
* 2023-04-26 04:26:37 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-26 04:26:37 (4199) [INFO] 
* 2023-04-26 04:27:01 (4213) [INFO] 
* 2023-04-26 04:27:01 (4213) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-26 04:27:01 (4213) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-26 04:27:02 (4230) [INFO] 
* 2023-04-26 04:27:02 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-26 04:27:02 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-26 04:27:02 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-26 04:27:02 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6wPp27ERf1/ea_profile.json
* 2023-04-26 04:27:02 (1805) [INFO] Backed up EA4 profile to /tmp/6wPp27ERf1/ea_profile.json
* 2023-04-26 04:27:02 (2856) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2023-04-26 04:27:03 (2856) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-04-26 04:27:03 (2965) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-26 04:27:03 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-27 04:27:28 (410) [INFO] Self-update of script version 7 requested.
* 2023-04-27 04:27:28 (415) [INFO] Newer version of script found. Downloading.
* 2023-04-27 04:27:28 (424) [INFO] Script update to version 8 successful.
* 2023-04-27 04:27:30 (363) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-27 04:27:30 (1573) [INFO] Checking if your system is up to date: 
* 2023-04-27 04:27:30 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-04-27 04:27:30 (3854) [INFO] 
* 2023-04-27 04:27:30 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-27 04:27:30 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-27 04:27:30 (3867) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-27 04:27:30 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-27 04:27:30 (3867) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-27 04:27:30 (3867) [INFO]               : zabbix zabbix-non-supported
* 2023-04-27 04:27:30 (3867) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-27 04:27:30 (3884) [INFO] 
* 2023-04-27 04:27:30 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-27 04:27:30 (3854) [INFO] 
* 2023-04-27 04:27:56 (3867) [INFO] 
* 2023-04-27 04:27:56 (3867) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-27 04:27:56 (3867) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-27 04:27:56 (3884) [INFO] 
* 2023-04-27 04:27:56 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-27 04:27:56 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-27 04:27:57 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-27 04:27:57 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-27 04:27:57 (1498) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-27 04:27:57 (1509) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-27 04:27:57 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101.
* 2023-04-27 04:27:57 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-28 04:26:24 (363) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-28 04:26:24 (1573) [INFO] Checking if your system is up to date: 
* 2023-04-28 04:26:24 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-04-28 04:26:24 (3854) [INFO] 
* 2023-04-28 04:26:24 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-28 04:26:24 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-28 04:26:24 (3867) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-28 04:26:24 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-28 04:26:24 (3867) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-28 04:26:24 (3867) [INFO]               : zabbix zabbix-non-supported
* 2023-04-28 04:26:24 (3867) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-28 04:26:24 (3884) [INFO] 
* 2023-04-28 04:26:24 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-28 04:26:24 (3854) [INFO] 
* 2023-04-28 04:26:49 (3867) [INFO] 
* 2023-04-28 04:26:49 (3867) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-28 04:26:49 (3867) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-28 04:26:49 (3884) [INFO] 
* 2023-04-28 04:26:49 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-28 04:26:49 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-28 04:26:51 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-28 04:26:51 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-28 04:26:51 (1498) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-28 04:26:51 (1509) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-28 04:26:51 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101.
* 2023-04-28 04:26:51 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-29 04:27:27 (363) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-29 04:27:27 (1573) [INFO] Checking if your system is up to date: 
* 2023-04-29 04:27:27 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-04-29 04:27:27 (3854) [INFO] 
* 2023-04-29 04:27:27 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-29 04:27:27 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-29 04:27:27 (3867) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-29 04:27:27 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-29 04:27:27 (3867) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-29 04:27:27 (3867) [INFO]               : zabbix zabbix-non-supported
* 2023-04-29 04:27:27 (3867) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-29 04:27:27 (3884) [INFO] 
* 2023-04-29 04:27:27 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-29 04:27:27 (3854) [INFO] 
* 2023-04-29 04:28:05 (3867) [INFO] 
* 2023-04-29 04:28:05 (3867) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-29 04:28:05 (3867) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-29 04:28:05 (3884) [INFO] 
* 2023-04-29 04:28:05 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-29 04:28:05 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-29 04:28:07 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-29 04:28:07 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-29 04:28:07 (1498) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-29 04:28:07 (1509) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-29 04:28:07 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101.
* 2023-04-29 04:28:07 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-30 04:27:11 (363) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-04-30 04:27:11 (1573) [INFO] Checking if your system is up to date: 
* 2023-04-30 04:27:11 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-04-30 04:27:11 (3854) [INFO] 
* 2023-04-30 04:27:11 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-30 04:27:12 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-30 04:27:12 (3867) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-30 04:27:12 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-04-30 04:27:12 (3867) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-30 04:27:12 (3867) [INFO]               : zabbix zabbix-non-supported
* 2023-04-30 04:27:12 (3867) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-04-30 04:27:12 (3884) [INFO] 
* 2023-04-30 04:27:12 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-30 04:27:12 (3854) [INFO] 
* 2023-04-30 04:27:37 (3867) [INFO] 
* 2023-04-30 04:27:37 (3867) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-04-30 04:27:37 (3867) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-04-30 04:27:37 (3884) [INFO] 
* 2023-04-30 04:27:37 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-30 04:27:37 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-30 04:27:39 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-04-30 04:27:39 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-04-30 04:27:39 (1498) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-04-30 04:27:39 (1509) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-04-30 04:27:39 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101.
* 2023-04-30 04:27:39 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-01 04:26:24 (363) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-01 04:26:24 (1573) [INFO] Checking if your system is up to date: 
* 2023-05-01 04:26:24 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-05-01 04:26:24 (3854) [INFO] 
* 2023-05-01 04:26:24 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-01 04:26:25 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-01 04:26:25 (3867) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-01 04:26:25 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-01 04:26:25 (3867) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-01 04:26:25 (3867) [INFO]               : zabbix zabbix-non-supported
* 2023-05-01 04:26:25 (3867) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-01 04:26:25 (3884) [INFO] 
* 2023-05-01 04:26:25 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-01 04:26:25 (3854) [INFO] 
* 2023-05-01 04:26:52 (3867) [INFO] 
* 2023-05-01 04:26:52 (3867) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-05-01 04:26:52 (3867) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-01 04:26:52 (3884) [INFO] 
* 2023-05-01 04:26:52 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-01 04:26:52 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-01 04:26:53 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-01 04:26:53 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-01 04:26:53 (1498) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-01 04:26:53 (1509) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-01 04:26:53 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101.
* 2023-05-01 04:26:53 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-02 04:26:27 (363) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-02 04:26:27 (1573) [INFO] Checking if your system is up to date: 
* 2023-05-02 04:26:27 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-05-02 04:26:27 (3854) [INFO] 
* 2023-05-02 04:26:27 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-02 04:26:27 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-02 04:26:27 (3867) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-02 04:26:27 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-02 04:26:27 (3867) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-02 04:26:27 (3867) [INFO]               : zabbix zabbix-non-supported
* 2023-05-02 04:26:28 (3867) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-02 04:26:28 (3884) [INFO] 
* 2023-05-02 04:26:28 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-02 04:26:28 (3854) [INFO] 
* 2023-05-02 04:26:53 (3867) [INFO] 
* 2023-05-02 04:26:53 (3867) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-05-02 04:26:53 (3867) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-02 04:26:53 (3884) [INFO] 
* 2023-05-02 04:26:53 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-02 04:26:53 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-02 04:26:54 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-02 04:26:54 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-02 04:26:54 (1498) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-02 04:26:54 (1509) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-02 04:26:54 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101.
* 2023-05-02 04:26:54 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-03 04:26:51 (144) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-03 04:26:51 (363) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-03 04:26:51 (1573) [INFO] Checking if your system is up to date: 
* 2023-05-03 04:26:51 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-05-03 04:26:51 (3854) [INFO] 
* 2023-05-03 04:26:52 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-03 04:26:52 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-03 04:26:52 (3867) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-03 04:26:52 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-03 04:26:52 (3867) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-03 04:26:52 (3867) [INFO]               : zabbix zabbix-non-supported
* 2023-05-03 04:26:52 (3867) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-03 04:26:52 (3884) [INFO] 
* 2023-05-03 04:26:52 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-03 04:26:52 (3854) [INFO] 
* 2023-05-03 04:27:30 (3867) [INFO] 
* 2023-05-03 04:27:30 (3867) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-05-03 04:27:30 (3867) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-03 04:27:30 (3884) [INFO] 
* 2023-05-03 04:27:30 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-03 04:27:30 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-03 04:27:32 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-03 04:27:32 (1498) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-03 04:27:32 (1498) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-03 04:27:32 (1509) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-03 04:27:32 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101.
* 2023-05-03 04:27:32 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-04 04:28:07 (145) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-04 04:28:08 (416) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-04 04:28:08 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-04 04:28:08 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-04 04:28:08 (3906) [INFO] 
* 2023-05-04 04:28:08 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-04 04:28:08 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-04 04:28:08 (3919) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-04 04:28:08 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-04 04:28:08 (3919) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-04 04:28:08 (3919) [INFO]               : zabbix zabbix-non-supported
* 2023-05-04 04:28:08 (3919) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-04 04:28:08 (3936) [INFO] 
* 2023-05-04 04:28:08 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-04 04:28:08 (3906) [INFO] 
* 2023-05-04 04:28:41 (3919) [INFO] 
* 2023-05-04 04:28:41 (3919) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-05-04 04:28:41 (3919) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-04 04:28:42 (3936) [INFO] 
* 2023-05-04 04:28:42 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-04 04:28:42 (145) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-04 04:28:43 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-04 04:28:43 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-04 04:28:43 (1550) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-04 04:28:43 (1561) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-04 04:28:43 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102.
* 2023-05-04 04:28:43 (246) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-05 04:26:30 (145) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-05 04:26:30 (416) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-05 04:26:30 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-05 04:26:30 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-05 04:26:30 (3906) [INFO] 
* 2023-05-05 04:26:31 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-05 04:26:31 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-05 04:26:31 (3919) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-05 04:26:31 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-05 04:26:31 (3919) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-05 04:26:31 (3919) [INFO]               : zabbix zabbix-non-supported
* 2023-05-05 04:26:31 (3919) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-05 04:26:31 (3936) [INFO] 
* 2023-05-05 04:26:31 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-05 04:26:31 (3906) [INFO] 
* 2023-05-05 04:26:58 (3919) [INFO] 
* 2023-05-05 04:26:58 (3919) [INFO] kernel.x86_64                     3.10.0-1160.88.1.el7                   updates
* 2023-05-05 04:26:58 (3919) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-05 04:26:58 (3936) [INFO] 
* 2023-05-05 04:26:58 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-05 04:26:58 (145) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-05 04:27:01 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-05 04:27:01 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-05 04:27:01 (1550) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-05 04:27:01 (1561) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-05 04:27:01 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102.
* 2023-05-05 04:27:01 (246) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-06 04:27:36 (145) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-06 04:27:36 (416) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-06 04:27:36 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-06 04:27:36 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-06 04:27:36 (3906) [INFO] 
* 2023-05-06 04:27:36 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-06 04:27:37 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-06 04:27:37 (3919) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-06 04:27:37 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-06 04:27:37 (3919) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-06 04:27:37 (3919) [INFO]               : zabbix zabbix-non-supported
* 2023-05-06 04:27:37 (3919) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-06 04:27:37 (3936) [INFO] 
* 2023-05-06 04:27:37 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-06 04:27:37 (3906) [INFO] 
* 2023-05-06 04:28:04 (3919) [INFO] 
* 2023-05-06 04:28:04 (3919) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-06 04:28:04 (3919) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-06 04:28:04 (3936) [INFO] 
* 2023-05-06 04:28:04 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-06 04:28:04 (145) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-06 04:28:06 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-06 04:28:06 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-06 04:28:06 (1550) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-06 04:28:06 (1561) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-06 04:28:06 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102.
* 2023-05-06 04:28:06 (246) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-07 04:27:19 (145) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-07 04:27:20 (416) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-07 04:27:20 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-07 04:27:20 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-07 04:27:20 (3906) [INFO] 
* 2023-05-07 04:27:20 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-07 04:27:20 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-07 04:27:20 (3919) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-07 04:27:20 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-07 04:27:20 (3919) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-07 04:27:20 (3919) [INFO]               : zabbix zabbix-non-supported
* 2023-05-07 04:27:20 (3919) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-07 04:27:20 (3936) [INFO] 
* 2023-05-07 04:27:20 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-07 04:27:20 (3906) [INFO] 
* 2023-05-07 04:27:52 (3919) [INFO] 
* 2023-05-07 04:27:52 (3919) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-07 04:27:52 (3919) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-07 04:27:53 (3936) [INFO] 
* 2023-05-07 04:27:53 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-07 04:27:53 (145) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-07 04:27:54 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-07 04:27:54 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-07 04:27:54 (1550) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-07 04:27:54 (1561) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-07 04:27:54 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102.
* 2023-05-07 04:27:54 (246) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-08 04:26:28 (145) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-08 04:26:29 (416) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-08 04:26:29 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-08 04:26:29 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-08 04:26:29 (3906) [INFO] 
* 2023-05-08 04:26:29 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-08 04:26:29 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-08 04:26:29 (3919) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-08 04:26:29 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-08 04:26:29 (3919) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-08 04:26:29 (3919) [INFO]               : zabbix zabbix-non-supported
* 2023-05-08 04:26:30 (3919) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-08 04:26:30 (3936) [INFO] 
* 2023-05-08 04:26:30 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-08 04:26:30 (3906) [INFO] 
* 2023-05-08 04:27:01 (3919) [INFO] 
* 2023-05-08 04:27:01 (3919) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-08 04:27:01 (3919) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-08 04:27:01 (3936) [INFO] 
* 2023-05-08 04:27:01 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-08 04:27:01 (145) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-08 04:27:03 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-08 04:27:03 (1550) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-08 04:27:03 (1550) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-08 04:27:03 (1561) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-08 04:27:03 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102.
* 2023-05-08 04:27:03 (246) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-09 04:26:32 (148) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-09 04:26:32 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-09 04:26:32 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-09 04:26:32 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-09 04:26:32 (3975) [INFO] 
* 2023-05-09 04:26:32 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-09 04:26:33 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-09 04:26:33 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-09 04:26:33 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-09 04:26:33 (3988) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-09 04:26:33 (3988) [INFO]               : zabbix zabbix-non-supported
* 2023-05-09 04:26:33 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-09 04:26:33 (4005) [INFO] 
* 2023-05-09 04:26:33 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-09 04:26:33 (3975) [INFO] 
* 2023-05-09 04:27:02 (3988) [INFO] 
* 2023-05-09 04:27:02 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-09 04:27:02 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-09 04:27:02 (4005) [INFO] 
* 2023-05-09 04:27:02 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-09 04:27:02 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-09 04:27:04 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-09 04:27:04 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-09 04:27:04 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-09 04:27:04 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-09 04:27:04 (148) [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-09 04:27:27 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-09 04:27:27 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lNPh7WoCao/ea_profile.json
* 2023-05-09 04:27:28 (2159) [INFO] Backed up EA4 profile to /tmp/lNPh7WoCao/ea_profile.json
* 2023-05-09 04:27:29 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-09 04:27:29 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-10 04:26:31 (148) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-10 04:26:32 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-10 04:26:32 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-10 04:26:32 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-10 04:26:32 (3975) [INFO] 
* 2023-05-10 04:26:32 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-10 04:26:33 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-10 04:26:33 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-10 04:26:33 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 letsencrypt-cpanel
* 2023-05-10 04:26:33 (3988) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-10 04:26:33 (3988) [INFO]               : zabbix zabbix-non-supported
* 2023-05-10 04:26:33 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-10 04:26:33 (4005) [INFO] 
* 2023-05-10 04:26:33 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-10 04:26:33 (3975) [INFO] 
* 2023-05-10 04:27:09 (3988) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-10 04:27:09 (3988) [INFO] Trying other mirror.
* 2023-05-10 04:27:30 (3988) [INFO] 
* 2023-05-10 04:27:30 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-10 04:27:30 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-10 04:27:30 (4005) [INFO] 
* 2023-05-10 04:27:30 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-10 04:27:30 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-10 04:27:32 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-10 04:27:32 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-10 04:27:32 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-10 04:27:32 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-10 04:27:32 (148) [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-10 04:27:56 (1525) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-10 04:27:56 (1526) [ERROR] https://mirror.team-cymru.com/remi/enterprise/7/safe/x86_64/repodata/20df475841016f8fdf05e214128fb5142161ebcf45b545803599661742174b2b-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

https://mirror.23m.com/remi/enterprise/7/safe/x86_64/repodata/20df475841016f8fdf05e214128fb5142161ebcf45b545803599661742174b2b-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mir01.syntis.net/remirepo/enterprise/7/safe/x86_64/repodata/20df475841016f8fdf05e214128fb5142161ebcf45b545803599661742174b2b-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
* 2023-05-10 04:27:56 (148) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-10 04:27:57 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-10 04:27:57 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S1W3tNGhrO/ea_profile.json
* 2023-05-10 04:27:57 (2159) [INFO] Backed up EA4 profile to /tmp/S1W3tNGhrO/ea_profile.json
* 2023-05-10 04:27:58 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-10 04:27:58 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-11 04:28:29 (148) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-11 04:28:30 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-11 04:28:30 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-11 04:28:30 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-11 04:28:30 (3975) [INFO] 
* 2023-05-11 04:28:30 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-11 04:28:30 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-11 04:28:30 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-11 04:28:30 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-11 04:28:30 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-11 04:28:30 (3988) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-11 04:28:30 (3988) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-11 04:28:31 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-11 04:28:31 (4005) [INFO] 
* 2023-05-11 04:28:31 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-11 04:28:31 (3975) [INFO] 
* 2023-05-11 04:28:58 (3988) [INFO] 
* 2023-05-11 04:28:58 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-11 04:28:58 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-11 04:28:58 (4005) [INFO] 
* 2023-05-11 04:28:58 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-11 04:28:58 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-11 04:28:59 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-11 04:28:59 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-11 04:28:59 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-11 04:28:59 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-11 04:28:59 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-11 04:28:59 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-11 04:28:59 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-11 04:28:59 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-11 04:28:59 (148) [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-11 04:29:24 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-11 04:29:24 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FwENRGKtPl/ea_profile.json
* 2023-05-11 04:29:25 (2159) [INFO] Backed up EA4 profile to /tmp/FwENRGKtPl/ea_profile.json
* 2023-05-11 04:29:25 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-11 04:29:25 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-12 04:26:29 (148) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-12 04:26:29 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-12 04:26:29 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-12 04:26:29 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-12 04:26:29 (3975) [INFO] 
* 2023-05-12 04:26:29 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-12 04:26:30 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-12 04:26:30 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-12 04:26:30 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-12 04:26:30 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-12 04:26:30 (3988) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-12 04:26:30 (3988) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-12 04:26:30 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-12 04:26:30 (4005) [INFO] 
* 2023-05-12 04:26:30 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-12 04:26:30 (3975) [INFO] 
* 2023-05-12 04:26:58 (3988) [INFO] 
* 2023-05-12 04:26:58 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-12 04:26:58 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-12 04:26:58 (4005) [INFO] 
* 2023-05-12 04:26:58 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-12 04:26:58 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-12 04:27:00 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-12 04:27:00 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-12 04:27:00 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-12 04:27:00 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-12 04:27:00 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-12 04:27:00 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-12 04:27:00 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-12 04:27:00 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-12 04:27:00 (148) [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-12 04:27:23 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-12 04:27:23 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vys4qX_VSY/ea_profile.json
* 2023-05-12 04:27:24 (2159) [INFO] Backed up EA4 profile to /tmp/vys4qX_VSY/ea_profile.json
* 2023-05-12 04:27:25 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-12 04:27:25 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-13 04:27:22 (148) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-13 04:27:23 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-13 04:27:23 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-13 04:27:23 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-13 04:27:23 (3975) [INFO] 
* 2023-05-13 04:27:23 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-13 04:27:23 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-13 04:27:23 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-13 04:27:23 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-13 04:27:23 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-13 04:27:23 (3988) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-13 04:27:23 (3988) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-13 04:27:24 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-13 04:27:24 (4005) [INFO] 
* 2023-05-13 04:27:24 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-13 04:27:24 (3975) [INFO] 
* 2023-05-13 04:27:57 (3988) [INFO] 
* 2023-05-13 04:27:57 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-13 04:27:57 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-13 04:27:57 (4005) [INFO] 
* 2023-05-13 04:27:57 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-13 04:27:57 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-13 04:27:59 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-13 04:27:59 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-13 04:27:59 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-13 04:27:59 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-13 04:27:59 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-13 04:27:59 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-13 04:27:59 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-13 04:27:59 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-13 04:27:59 (148) [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-13 04:28:23 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-13 04:28:23 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SBJjHRQRPD/ea_profile.json
* 2023-05-13 04:28:24 (2159) [INFO] Backed up EA4 profile to /tmp/SBJjHRQRPD/ea_profile.json
* 2023-05-13 04:28:25 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-13 04:28:25 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-14 04:27:35 (148) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-14 04:27:35 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-14 04:27:35 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-14 04:27:35 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-14 04:27:35 (3975) [INFO] 
* 2023-05-14 04:27:36 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-14 04:27:36 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-14 04:27:36 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-14 04:27:36 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-14 04:27:36 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-14 04:27:36 (3988) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-14 04:27:36 (3988) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-14 04:27:36 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-14 04:27:36 (4005) [INFO] 
* 2023-05-14 04:27:36 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-14 04:27:36 (3975) [INFO] 
* 2023-05-14 04:28:05 (3988) [INFO] 
* 2023-05-14 04:28:05 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-14 04:28:05 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-14 04:28:05 (4005) [INFO] 
* 2023-05-14 04:28:05 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-14 04:28:05 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-14 04:28:08 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-14 04:28:08 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-14 04:28:08 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-14 04:28:08 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-14 04:28:08 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-14 04:28:08 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-14 04:28:08 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-14 04:28:08 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-14 04:28:08 (148) [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-14 04:28:32 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-14 04:28:32 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hMqV2XdmmL/ea_profile.json
* 2023-05-14 04:28:33 (2159) [INFO] Backed up EA4 profile to /tmp/hMqV2XdmmL/ea_profile.json
* 2023-05-14 04:28:34 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-14 04:28:34 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-15 04:26:30 (148) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-15 04:26:31 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-15 04:26:31 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-15 04:26:31 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-15 04:26:31 (3975) [INFO] 
* 2023-05-15 04:26:31 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-15 04:26:32 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-15 04:26:32 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-15 04:26:32 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-15 04:26:32 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-15 04:26:32 (3988) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-15 04:26:32 (3988) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-15 04:26:32 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-15 04:26:32 (4005) [INFO] 
* 2023-05-15 04:26:32 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-15 04:26:32 (3975) [INFO] 
* 2023-05-15 04:27:04 (3988) [INFO] 
* 2023-05-15 04:27:04 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-15 04:27:04 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-15 04:27:04 (4005) [INFO] 
* 2023-05-15 04:27:04 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-15 04:27:04 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-15 04:27:05 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-15 04:27:05 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-15 04:27:05 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-15 04:27:05 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-15 04:27:05 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-15 04:27:05 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-15 04:27:05 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-15 04:27:05 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-15 04:27:05 (148) [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-15 04:27:35 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-15 04:27:35 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cuK9_ZxwGG/ea_profile.json
* 2023-05-15 04:27:36 (2159) [INFO] Backed up EA4 profile to /tmp/cuK9_ZxwGG/ea_profile.json
* 2023-05-15 04:27:37 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-15 04:27:37 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-16 04:26:36 (148) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.108.0.15) does not appear to be up to date.
Please upgrade cPanel to a most recent version. 

* 2023-05-16 04:26:36 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-16 04:26:36 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-16 04:26:36 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-16 04:26:36 (3975) [INFO] 
* 2023-05-16 04:26:37 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-16 04:26:37 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-16 04:26:37 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-16 04:26:37 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-16 04:26:37 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-16 04:26:37 (3988) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-16 04:26:37 (3988) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-16 04:26:37 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-16 04:26:37 (4005) [INFO] 
* 2023-05-16 04:26:37 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-16 04:26:37 (3975) [INFO] 
* 2023-05-16 04:27:09 (3988) [INFO] 
* 2023-05-16 04:27:09 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-16 04:27:09 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-16 04:27:09 (4005) [INFO] 
* 2023-05-16 04:27:09 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-16 04:27:09 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-16 04:27:11 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-16 04:27:11 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-16 04:27:11 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-16 04:27:11 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-16 04:27:11 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-16 04:27:11 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-16 04:27:11 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-16 04:27:11 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-16 04:27:11 (148) [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-16 04:27:37 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-16 04:27:37 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gGgRBJkaeS/ea_profile.json
* 2023-05-16 04:27:38 (2159) [INFO] Backed up EA4 profile to /tmp/gGgRBJkaeS/ea_profile.json
* 2023-05-16 04:27:38 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-16 04:27:38 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-17 04:28:12 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-17 04:28:12 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-17 04:28:12 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-17 04:28:12 (3975) [INFO] 
* 2023-05-17 04:28:13 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-17 04:28:13 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-17 04:28:13 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-17 04:28:13 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-17 04:28:13 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-17 04:28:13 (3988) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-17 04:28:13 (3988) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-17 04:28:13 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-17 04:28:13 (4005) [INFO] 
* 2023-05-17 04:28:13 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-17 04:28:13 (3975) [INFO] 
* 2023-05-17 04:28:40 (3988) [INFO] 
* 2023-05-17 04:28:40 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-17 04:28:40 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-17 04:28:40 (4005) [INFO] 
* 2023-05-17 04:28:40 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-17 04:28:40 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-17 04:28:42 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-17 04:28:42 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-17 04:28:42 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-17 04:28:42 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-17 04:28:42 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-17 04:28:42 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-17 04:28:42 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-17 04:28:42 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-17 04:28:42 (148) [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-17 04:29:07 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-17 04:29:07 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wL4Fd7W2qK/ea_profile.json
* 2023-05-17 04:29:08 (2159) [INFO] Backed up EA4 profile to /tmp/wL4Fd7W2qK/ea_profile.json
* 2023-05-17 04:29:08 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-17 04:29:08 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-18 04:27:40 (423) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-18 04:27:40 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-18 04:27:40 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-18 04:27:40 (3975) [INFO] 
* 2023-05-18 04:27:40 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-18 04:27:40 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-18 04:27:40 (3988) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-18 04:27:40 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-18 04:27:40 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-18 04:27:40 (3988) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-18 04:27:40 (3988) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-18 04:27:40 (3988) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-18 04:27:40 (4005) [INFO] 
* 2023-05-18 04:27:40 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-18 04:27:40 (3975) [INFO] 
* 2023-05-18 04:28:08 (3988) [INFO] 
* 2023-05-18 04:28:08 (3988) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-18 04:28:08 (3988) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-18 04:28:08 (4005) [INFO] 
* 2023-05-18 04:28:08 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-18 04:28:08 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-18 04:28:09 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-18 04:28:09 (1584) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-18 04:28:09 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-18 04:28:09 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-18 04:28:09 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-18 04:28:09 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-18 04:28:09 (1584) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-18 04:28:09 (1595) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-18 04:28:09 (148) [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-18 04:28:35 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-18 04:28:35 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cQ4dplZSog/ea_profile.json
* 2023-05-18 04:28:36 (2159) [INFO] Backed up EA4 profile to /tmp/cQ4dplZSog/ea_profile.json
* 2023-05-18 04:28:37 (148) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-18 04:28:37 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-19 04:26:45 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-19 04:26:45 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-19 04:26:45 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-19 04:26:45 (4086) [INFO] 
* 2023-05-19 04:26:45 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-19 04:26:45 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-19 04:26:45 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-19 04:26:45 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-19 04:26:45 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-19 04:26:45 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-19 04:26:45 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-19 04:26:45 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-19 04:26:45 (4116) [INFO] 
* 2023-05-19 04:26:45 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-19 04:26:45 (4086) [INFO] 
* 2023-05-19 04:27:13 (4099) [INFO] 
* 2023-05-19 04:27:13 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-19 04:27:13 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-19 04:27:13 (4116) [INFO] 
* 2023-05-19 04:27:13 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-19 04:27:13 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-19 04:27:15 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-19 04:27:15 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-19 04:27:15 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-19 04:27:15 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-19 04:27: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-05-19 04:27:39 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-19 04:27:39 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kha1vL01wb/ea_profile.json
* 2023-05-19 04:27:40 (2258) [INFO] Backed up EA4 profile to /tmp/Kha1vL01wb/ea_profile.json
* 2023-05-19 04:27:41 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-19 04:27:41 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-20 04:27:13 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-20 04:27:13 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-20 04:27:13 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-20 04:27:13 (4086) [INFO] 
* 2023-05-20 04:27:13 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-20 04:27:13 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-20 04:27:13 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-20 04:27:13 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-20 04:27:13 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-20 04:27:13 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-20 04:27:13 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-20 04:27:14 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-20 04:27:14 (4116) [INFO] 
* 2023-05-20 04:27:14 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-20 04:27:14 (4086) [INFO] 
* 2023-05-20 04:27:42 (4099) [INFO] 
* 2023-05-20 04:27:42 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-20 04:27:42 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-20 04:27:43 (4116) [INFO] 
* 2023-05-20 04:27:43 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-20 04:27:43 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-20 04:27:44 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-20 04:27:44 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-20 04:27:44 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-20 04:27:44 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-20 04:27: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-05-20 04:28:08 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-20 04:28:08 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/K9sdyzEjMl/ea_profile.json
* 2023-05-20 04:28:09 (2258) [INFO] Backed up EA4 profile to /tmp/K9sdyzEjMl/ea_profile.json
* 2023-05-20 04:28:10 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-20 04:28:10 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-21 04:27:21 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-21 04:27:21 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-21 04:27:21 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-21 04:27:21 (4086) [INFO] 
* 2023-05-21 04:27:22 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-21 04:27:22 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-21 04:27:22 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-21 04:27:22 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-21 04:27:22 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-21 04:27:22 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-21 04:27:22 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-21 04:27:22 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-21 04:27:22 (4116) [INFO] 
* 2023-05-21 04:27:22 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-21 04:27:22 (4086) [INFO] 
* 2023-05-21 04:27:50 (4099) [INFO] 
* 2023-05-21 04:27:50 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-21 04:27:50 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-21 04:27:50 (4116) [INFO] 
* 2023-05-21 04:27:50 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-21 04:27:50 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-21 04:27:52 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-21 04:27:52 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-21 04:27:52 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-21 04:27:52 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-21 04:27: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-21 04:28:17 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-21 04:28:17 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VhXbQuebKV/ea_profile.json
* 2023-05-21 04:28:18 (2258) [INFO] Backed up EA4 profile to /tmp/VhXbQuebKV/ea_profile.json
* 2023-05-21 04:28:18 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-21 04:28:18 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-22 04:26:27 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-22 04:26:27 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-22 04:26:27 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-22 04:26:27 (4086) [INFO] 
* 2023-05-22 04:26:27 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-22 04:26:27 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-22 04:26:27 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-22 04:26:27 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-22 04:26:27 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-22 04:26:27 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-22 04:26:27 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-22 04:26:27 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-22 04:26:27 (4116) [INFO] 
* 2023-05-22 04:26:27 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-22 04:26:27 (4086) [INFO] 
* 2023-05-22 04:26:56 (4099) [INFO] 
* 2023-05-22 04:26:56 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-22 04:26:56 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-22 04:26:56 (4116) [INFO] 
* 2023-05-22 04:26:56 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-22 04:26:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-22 04:26:58 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-22 04:26:58 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-22 04:26:58 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-22 04:26:58 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-22 04:26: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-05-22 04:27:22 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-22 04:27:22 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5SKtTBwIS7/ea_profile.json
* 2023-05-22 04:27:23 (2258) [INFO] Backed up EA4 profile to /tmp/5SKtTBwIS7/ea_profile.json
* 2023-05-22 04:27:23 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-22 04:27:23 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-23 04:26:55 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-23 04:26:55 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-23 04:26:55 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-23 04:26:55 (4086) [INFO] 
* 2023-05-23 04:26:55 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-23 04:26:55 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-23 04:26:55 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-23 04:26:55 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-23 04:26:55 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-23 04:26:55 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-23 04:26:55 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-23 04:26:55 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-23 04:26:55 (4116) [INFO] 
* 2023-05-23 04:26:55 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-23 04:26:55 (4086) [INFO] 
* 2023-05-23 04:27:22 (4099) [INFO] 
* 2023-05-23 04:27:22 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-23 04:27:22 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-23 04:27:22 (4116) [INFO] 
* 2023-05-23 04:27:22 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-23 04:27:22 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-23 04:27:24 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-23 04:27:24 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-23 04:27:24 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-23 04:27:24 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-23 04:27: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-23 04:27:48 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-23 04:27:48 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k2875euf_1/ea_profile.json
* 2023-05-23 04:27:49 (2258) [INFO] Backed up EA4 profile to /tmp/k2875euf_1/ea_profile.json
* 2023-05-23 04:27:50 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-23 04:27:50 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-24 04:26:32 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-24 04:26:32 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-24 04:26:32 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-24 04:26:32 (4086) [INFO] 
* 2023-05-24 04:26:32 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-24 04:26:32 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-24 04:26:32 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-24 04:26:32 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-24 04:26:32 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-24 04:26:32 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-24 04:26:32 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-24 04:26:33 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-24 04:26:33 (4116) [INFO] 
* 2023-05-24 04:26:33 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-24 04:26:33 (4086) [INFO] 
* 2023-05-24 04:26:59 (4099) [INFO] 
* 2023-05-24 04:26:59 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-24 04:26:59 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-24 04:26:59 (4116) [INFO] 
* 2023-05-24 04:26:59 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-24 04:26:59 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-24 04:27:02 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-24 04:27:02 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-24 04:27:02 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-24 04:27:02 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-24 04:27: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-05-24 04:27:26 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-24 04:27:26 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EEVl7fAfEK/ea_profile.json
* 2023-05-24 04:27:27 (2258) [INFO] Backed up EA4 profile to /tmp/EEVl7fAfEK/ea_profile.json
* 2023-05-24 04:27:27 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-24 04:27:27 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-25 04:28:02 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-25 04:28:02 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-25 04:28:02 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-25 04:28:02 (4086) [INFO] 
* 2023-05-25 04:28:03 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-25 04:28:03 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-25 04:28:03 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-25 04:28:03 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-25 04:28:03 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-25 04:28:03 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-25 04:28:03 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-25 04:28:03 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-25 04:28:03 (4116) [INFO] 
* 2023-05-25 04:28:03 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-25 04:28:03 (4086) [INFO] 
* 2023-05-25 04:28:31 (4099) [INFO] 
* 2023-05-25 04:28:31 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-25 04:28:31 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-25 04:28:31 (4116) [INFO] 
* 2023-05-25 04:28:31 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-25 04:28:31 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-25 04:28:32 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-25 04:28:32 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-25 04:28:32 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-25 04:28:32 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-25 04:28:32 (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 04:29:00 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-25 04:29:00 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/byNyyIQfLb/ea_profile.json
* 2023-05-25 04:29:01 (2258) [INFO] Backed up EA4 profile to /tmp/byNyyIQfLb/ea_profile.json
* 2023-05-25 04:29:01 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-25 04:29:02 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-26 04:26:28 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-26 04:26:28 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-26 04:26:28 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-26 04:26:28 (4086) [INFO] 
* 2023-05-26 04:26:29 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-26 04:26:29 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-26 04:26:29 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-26 04:26:29 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-26 04:26:29 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-26 04:26:29 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-26 04:26:29 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-26 04:26:29 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-26 04:26:29 (4116) [INFO] 
* 2023-05-26 04:26:29 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-26 04:26:29 (4086) [INFO] 
* 2023-05-26 04:26:57 (4099) [INFO] 
* 2023-05-26 04:26:57 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-26 04:26:57 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-26 04:26:57 (4116) [INFO] 
* 2023-05-26 04:26:57 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-26 04:26:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-26 04:26:58 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-26 04:26:58 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-26 04:26:58 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-26 04:26:58 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-26 04:26: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-05-26 04:27:23 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-26 04:27:23 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dMTxkb1Xn1/ea_profile.json
* 2023-05-26 04:27:24 (2258) [INFO] Backed up EA4 profile to /tmp/dMTxkb1Xn1/ea_profile.json
* 2023-05-26 04:27:25 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-26 04:27:25 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-27 04:27:19 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-27 04:27:19 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-27 04:27:19 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-27 04:27:19 (4086) [INFO] 
* 2023-05-27 04:27:19 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-27 04:27:19 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-27 04:27:19 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-27 04:27:19 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-27 04:27:19 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-27 04:27:19 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-27 04:27:19 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-27 04:27:19 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-27 04:27:19 (4116) [INFO] 
* 2023-05-27 04:27:19 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-27 04:27:19 (4086) [INFO] 
* 2023-05-27 04:27:47 (4099) [INFO] 
* 2023-05-27 04:27:47 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-27 04:27:47 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-27 04:27:47 (4116) [INFO] 
* 2023-05-27 04:27:47 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-27 04:27:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-27 04:27:49 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-27 04:27:49 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-27 04:27:49 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-27 04:27:49 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-27 04:27: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-05-27 04:28:14 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-27 04:28:14 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bhchYeRv3A/ea_profile.json
* 2023-05-27 04:28:15 (2258) [INFO] Backed up EA4 profile to /tmp/bhchYeRv3A/ea_profile.json
* 2023-05-27 04:28:15 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-27 04:28:15 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-28 04:27:24 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-28 04:27:24 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-28 04:27:24 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-28 04:27:24 (4086) [INFO] 
* 2023-05-28 04:27:25 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-28 04:27:25 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-28 04:27:25 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-28 04:27:25 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-28 04:27:25 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-28 04:27:25 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-28 04:27:25 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-28 04:27:25 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-28 04:27:25 (4116) [INFO] 
* 2023-05-28 04:27:25 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-28 04:27:25 (4086) [INFO] 
* 2023-05-28 04:27:56 (4099) [INFO] 
* 2023-05-28 04:27:56 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-28 04:27:56 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-28 04:27:56 (4116) [INFO] 
* 2023-05-28 04:27:56 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-28 04:27:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-28 04:27:58 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-28 04:27:58 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-28 04:27:58 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-28 04:27:58 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-28 04:27: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-05-28 04:28:25 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-28 04:28:25 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3YVBEBICdI/ea_profile.json
* 2023-05-28 04:28:26 (2258) [INFO] Backed up EA4 profile to /tmp/3YVBEBICdI/ea_profile.json
* 2023-05-28 04:28:27 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-28 04:28:27 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-29 04:26:23 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-29 04:26:23 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-29 04:26:23 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-29 04:26:23 (4086) [INFO] 
* 2023-05-29 04:26:23 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-29 04:26:23 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-29 04:26:23 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-29 04:26:23 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-29 04:26:23 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-29 04:26:23 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-29 04:26:23 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-29 04:26:23 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-29 04:26:23 (4116) [INFO] 
* 2023-05-29 04:26:23 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-29 04:26:23 (4086) [INFO] 
* 2023-05-29 04:26:51 (4099) [INFO] 
* 2023-05-29 04:26:51 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-29 04:26:51 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-29 04:26:51 (4116) [INFO] 
* 2023-05-29 04:26:51 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-29 04:26:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-29 04:26:53 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-29 04:26:53 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-29 04:26:53 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-29 04:26:53 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-29 04:26: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-29 04:27:18 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-29 04:27:18 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZZoT3Xdi9U/ea_profile.json
* 2023-05-29 04:27:19 (2258) [INFO] Backed up EA4 profile to /tmp/ZZoT3Xdi9U/ea_profile.json
* 2023-05-29 04:27:19 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-29 04:27:19 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-30 04:26:29 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-30 04:26:29 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-30 04:26:29 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-30 04:26:29 (4086) [INFO] 
* 2023-05-30 04:26:29 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-30 04:26:29 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-30 04:26:29 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-30 04:26:29 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-30 04:26:29 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-30 04:26:29 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-30 04:26:29 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-30 04:26:30 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-30 04:26:30 (4116) [INFO] 
* 2023-05-30 04:26:30 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-30 04:26:30 (4086) [INFO] 
* 2023-05-30 04:27:01 (4099) [INFO] 
* 2023-05-30 04:27:01 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-30 04:27:01 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-30 04:27:01 (4116) [INFO] 
* 2023-05-30 04:27:01 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-30 04:27:01 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-30 04:27:02 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-30 04:27:02 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-30 04:27:02 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-30 04:27:02 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-30 04:27: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-05-30 04:27:26 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-30 04:27:26 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2aTx7GeaDQ/ea_profile.json
* 2023-05-30 04:27:27 (2258) [INFO] Backed up EA4 profile to /tmp/2aTx7GeaDQ/ea_profile.json
* 2023-05-30 04:27:28 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-30 04:27:28 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-31 04:26:42 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-05-31 04:26:42 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-31 04:26:42 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-31 04:26:42 (4086) [INFO] 
* 2023-05-31 04:26:43 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-31 04:26:43 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-31 04:26:43 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-31 04:26:43 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-31 04:26:43 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-31 04:26:43 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-05-31 04:26:43 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-05-31 04:26:43 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-05-31 04:26:43 (4116) [INFO] 
* 2023-05-31 04:26:43 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-31 04:26:43 (4086) [INFO] 
* 2023-05-31 04:27:11 (4099) [INFO] 
* 2023-05-31 04:27:11 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-05-31 04:27:11 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-05-31 04:27:11 (4116) [INFO] 
* 2023-05-31 04:27:11 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-31 04:27:11 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-31 04:27:13 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-05-31 04:27:13 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-05-31 04:27:13 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-05-31 04:27:13 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-05-31 04:27: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-05-31 04:27:41 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-31 04:27:41 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UfujpLWf7V/ea_profile.json
* 2023-05-31 04:27:42 (2258) [INFO] Backed up EA4 profile to /tmp/UfujpLWf7V/ea_profile.json
* 2023-05-31 04:27:42 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-05-31 04:27:42 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-06-01 04:28:01 (459) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-01 04:28:01 (1699) [INFO] Checking if your system is up to date: 
* 2023-06-01 04:28:01 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-06-01 04:28:01 (4086) [INFO] 
* 2023-06-01 04:28:01 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-01 04:28:02 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-01 04:28:02 (4099) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-01 04:28:02 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-01 04:28:02 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-01 04:28:02 (4099) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-01 04:28:02 (4099) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-01 04:28:02 (4099) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-01 04:28:02 (4116) [INFO] 
* 2023-06-01 04:28:02 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-01 04:28:02 (4086) [INFO] 
* 2023-06-01 04:28:29 (4099) [INFO] 
* 2023-06-01 04:28:29 (4099) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-01 04:28:29 (4099) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-01 04:28:29 (4116) [INFO] 
* 2023-06-01 04:28:29 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-01 04:28:29 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-01 04:28:30 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-01 04:28:30 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-01 04:28:30 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-01 04:28:30 (1635) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-01 04:28: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-06-01 04:28:55 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-01 04:28:55 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n0JRzJvjb8/ea_profile.json
* 2023-06-01 04:28:56 (2258) [INFO] Backed up EA4 profile to /tmp/n0JRzJvjb8/ea_profile.json
* 2023-06-01 04:28:56 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-01 04:28:56 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-06-02 04:27:28 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-02 04:27:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-02 04:27:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-02 04:27:28 (4089) [INFO] 
* 2023-06-02 04:27:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-02 04:27:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-02 04:27:28 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-02 04:27:28 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-02 04:27:28 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-02 04:27:28 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-02 04:27:28 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-02 04:27:28 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-02 04:27:28 (4119) [INFO] 
* 2023-06-02 04:27:28 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-02 04:27:28 (4089) [INFO] 
* 2023-06-02 04:27:57 (4102) [INFO] 
* 2023-06-02 04:27:57 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-02 04:27:57 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-02 04:27:57 (4119) [INFO] 
* 2023-06-02 04:27:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-02 04:27:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-02 04:27:59 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-02 04:27:59 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-02 04:27:59 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-02 04:27:59 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-02 04:27: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-06-02 04:28:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-02 04:28:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JGCoyfmfjH/ea_profile.json
* 2023-06-02 04:28:25 (2259) [INFO] Backed up EA4 profile to /tmp/JGCoyfmfjH/ea_profile.json
* 2023-06-02 04:28:25 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-02 04:28:25 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-03 04:27:23 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-03 04:27:23 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-03 04:27:23 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-03 04:27:23 (4089) [INFO] 
* 2023-06-03 04:27:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-03 04:27:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-03 04:27:24 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-03 04:27:24 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-03 04:27:24 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-03 04:27:24 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-03 04:27:24 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-03 04:27:24 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-03 04:27:24 (4119) [INFO] 
* 2023-06-03 04:27:24 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-03 04:27:24 (4089) [INFO] 
* 2023-06-03 04:27:50 (4102) [INFO] 
* 2023-06-03 04:27:50 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-03 04:27:50 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-03 04:27:51 (4119) [INFO] 
* 2023-06-03 04:27:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-03 04:27:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-03 04:27:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-03 04:27:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-03 04:27:53 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-03 04:27:53 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-03 04:27: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-03 04:28:17 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-03 04:28:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/s2Itejru1j/ea_profile.json
* 2023-06-03 04:28:18 (2259) [INFO] Backed up EA4 profile to /tmp/s2Itejru1j/ea_profile.json
* 2023-06-03 04:28:18 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-03 04:28:19 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-04 04:27:13 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-04 04:27:13 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-04 04:27:13 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-04 04:27:13 (4089) [INFO] 
* 2023-06-04 04:27:13 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-04 04:27:13 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-04 04:27:13 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-04 04:27:13 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-04 04:27:13 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-04 04:27:13 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-04 04:27:13 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-04 04:27:14 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-04 04:27:14 (4119) [INFO] 
* 2023-06-04 04:27:14 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-04 04:27:14 (4089) [INFO] 
* 2023-06-04 04:27:41 (4102) [INFO] 
* 2023-06-04 04:27:41 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-04 04:27:41 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-04 04:27:41 (4119) [INFO] 
* 2023-06-04 04:27:41 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-04 04:27:41 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-04 04:27:44 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-04 04:27:44 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-04 04:27:44 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-04 04:27:44 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-04 04:27: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-04 04:28:08 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-04 04:28:08 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NPW0Nicprw/ea_profile.json
* 2023-06-04 04:28:09 (2259) [INFO] Backed up EA4 profile to /tmp/NPW0Nicprw/ea_profile.json
* 2023-06-04 04:28:10 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-04 04:28:10 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-05 04:26:24 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-05 04:26:24 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-05 04:26:24 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-05 04:26:24 (4089) [INFO] 
* 2023-06-05 04:26:25 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-05 04:26:25 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-05 04:26:25 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-05 04:26:25 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-05 04:26:25 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-05 04:26:25 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-05 04:26:25 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-05 04:26:25 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-05 04:26:25 (4119) [INFO] 
* 2023-06-05 04:26:25 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-05 04:26:25 (4089) [INFO] 
* 2023-06-05 04:26:53 (4102) [INFO] 
* 2023-06-05 04:26:53 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-05 04:26:53 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-05 04:26:53 (4119) [INFO] 
* 2023-06-05 04:26:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-05 04:26:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-05 04:26:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-05 04:26:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-05 04:26:55 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-05 04:26:55 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-05 04:26: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-05 04:27:22 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-05 04:27:22 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NSp02gWpjL/ea_profile.json
* 2023-06-05 04:27:23 (2259) [INFO] Backed up EA4 profile to /tmp/NSp02gWpjL/ea_profile.json
* 2023-06-05 04:27:23 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-05 04:27:23 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-06 04:26:23 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-06 04:26:23 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-06 04:26:23 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-06 04:26:23 (4089) [INFO] 
* 2023-06-06 04:26:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-06 04:26:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-06 04:26:24 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-06 04:26:24 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-06 04:26:24 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-06 04:26:24 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-06 04:26:24 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-06 04:26:24 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-06 04:26:24 (4119) [INFO] 
* 2023-06-06 04:26:24 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-06 04:26:24 (4089) [INFO] 
* 2023-06-06 04:26:51 (4102) [INFO] 
* 2023-06-06 04:26:51 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-06 04:26:51 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-06 04:26:51 (4119) [INFO] 
* 2023-06-06 04:26:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-06 04:26:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-06 04:26:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-06 04:26:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-06 04:26:53 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-06 04:26:53 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-06 04:26: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-06 04:27:18 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-06 04:27:18 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W7s8F1vb06/ea_profile.json
* 2023-06-06 04:27:19 (2259) [INFO] Backed up EA4 profile to /tmp/W7s8F1vb06/ea_profile.json
* 2023-06-06 04:27:20 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-06 04:27:20 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-07 04:26:22 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-07 04:26:22 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-07 04:26:22 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-07 04:26:22 (4089) [INFO] 
* 2023-06-07 04:26:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-07 04:26:23 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-07 04:26:23 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-07 04:26:23 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-07 04:26:23 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-07 04:26:23 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-07 04:26:23 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-07 04:26:23 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-07 04:26:23 (4119) [INFO] 
* 2023-06-07 04:26:23 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-07 04:26:23 (4089) [INFO] 
* 2023-06-07 04:26:50 (4102) [INFO] 
* 2023-06-07 04:26:50 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-07 04:26:50 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-07 04:26:50 (4119) [INFO] 
* 2023-06-07 04:26:50 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-07 04:26:50 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-07 04:26:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-07 04:26:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-07 04:26:52 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-07 04:26:52 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-07 04:26: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-07 04:27:16 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-07 04:27:16 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WIuT8Yu6tk/ea_profile.json
* 2023-06-07 04:27:17 (2259) [INFO] Backed up EA4 profile to /tmp/WIuT8Yu6tk/ea_profile.json
* 2023-06-07 04:27:18 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-07 04:27:18 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-08 04:27:03 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-08 04:27:03 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-08 04:27:03 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-08 04:27:03 (4089) [INFO] 
* 2023-06-08 04:27:03 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-08 04:27:03 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-08 04:27:03 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-08 04:27:03 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-08 04:27:03 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-08 04:27:03 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-08 04:27:03 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-08 04:27:04 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-08 04:27:04 (4119) [INFO] 
* 2023-06-08 04:27:04 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-08 04:27:04 (4089) [INFO] 
* 2023-06-08 04:27:30 (4102) [INFO] 
* 2023-06-08 04:27:30 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-08 04:27:30 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-08 04:27:31 (4119) [INFO] 
* 2023-06-08 04:27:31 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-08 04:27:31 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-08 04:27:32 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-08 04:27:32 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-08 04:27:32 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-08 04:27:32 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-08 04:27:32 (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 04:28:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-08 04:28:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DZzccSdfx4/ea_profile.json
* 2023-06-08 04:28:01 (2259) [INFO] Backed up EA4 profile to /tmp/DZzccSdfx4/ea_profile.json
* 2023-06-08 04:28:01 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-08 04:28:01 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-09 04:26:27 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-09 04:26:27 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-09 04:26:27 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-09 04:26:27 (4089) [INFO] 
* 2023-06-09 04:26:27 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-09 04:26:27 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-09 04:26:27 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-09 04:26:27 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-09 04:26:27 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-09 04:26:27 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-09 04:26:27 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-09 04:26:27 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-09 04:26:27 (4119) [INFO] 
* 2023-06-09 04:26:27 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-09 04:26:27 (4089) [INFO] 
* 2023-06-09 04:26:56 (4102) [INFO] 
* 2023-06-09 04:26:56 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-09 04:26:56 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-09 04:26:56 (4119) [INFO] 
* 2023-06-09 04:26:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-09 04:26:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-09 04:26:58 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-09 04:26:58 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-09 04:26:58 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-09 04:26:58 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-09 04:26: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-09 04:27:23 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-09 04:27:23 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EA2_ZKw5Q9/ea_profile.json
* 2023-06-09 04:27:24 (2259) [INFO] Backed up EA4 profile to /tmp/EA2_ZKw5Q9/ea_profile.json
* 2023-06-09 04:27:25 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-09 04:27:25 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-10 04:27:18 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-10 04:27:18 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-10 04:27:18 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-10 04:27:18 (4089) [INFO] 
* 2023-06-10 04:27:18 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-10 04:27:18 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-10 04:27:18 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-10 04:27:18 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-10 04:27:18 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-10 04:27:18 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-10 04:27:18 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-10 04:27:18 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-10 04:27:18 (4119) [INFO] 
* 2023-06-10 04:27:18 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-10 04:27:18 (4089) [INFO] 
* 2023-06-10 04:27:46 (4102) [INFO] 
* 2023-06-10 04:27:46 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-10 04:27:46 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-10 04:27:46 (4119) [INFO] 
* 2023-06-10 04:27:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-10 04:27:46 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-10 04:27:48 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-10 04:27:48 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-10 04:27:48 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-10 04:27:48 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-10 04:27: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-10 04:28:14 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-10 04:28:14 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KFHwvQUlol/ea_profile.json
* 2023-06-10 04:28:15 (2259) [INFO] Backed up EA4 profile to /tmp/KFHwvQUlol/ea_profile.json
* 2023-06-10 04:28:15 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-10 04:28:15 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-11 04:27:16 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-11 04:27:16 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-11 04:27:16 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-11 04:27:16 (4089) [INFO] 
* 2023-06-11 04:27:17 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-11 04:27:17 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-11 04:27:17 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-11 04:27:17 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-11 04:27:17 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-11 04:27:17 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-11 04:27:17 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-11 04:27:17 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-11 04:27:17 (4119) [INFO] 
* 2023-06-11 04:27:17 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-11 04:27:17 (4089) [INFO] 
* 2023-06-11 04:27:43 (4102) [INFO] 
* 2023-06-11 04:27:43 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-11 04:27:43 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-11 04:27:43 (4119) [INFO] 
* 2023-06-11 04:27:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-11 04:27:43 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-11 04:27:45 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-11 04:27:45 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-11 04:27:45 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-11 04:27:45 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-11 04:27: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-11 04:28:17 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-11 04:28:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oEVn2DJm4o/ea_profile.json
* 2023-06-11 04:28:17 (2259) [INFO] Backed up EA4 profile to /tmp/oEVn2DJm4o/ea_profile.json
* 2023-06-11 04:28:18 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-11 04:28:18 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-12 04:26:21 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-12 04:26:21 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-12 04:26:21 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-12 04:26:21 (4089) [INFO] 
* 2023-06-12 04:26:21 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-12 04:26:21 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-12 04:26:21 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-12 04:26:21 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-12 04:26:21 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-12 04:26:21 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-12 04:26:21 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-12 04:26:21 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-12 04:26:21 (4119) [INFO] 
* 2023-06-12 04:26:21 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-12 04:26:21 (4089) [INFO] 
* 2023-06-12 04:26:47 (4102) [INFO] 
* 2023-06-12 04:26:47 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-12 04:26:47 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-12 04:26:47 (4119) [INFO] 
* 2023-06-12 04:26:47 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-12 04:26:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-12 04:26:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-12 04:26:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-12 04:26:49 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-12 04:26:49 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-12 04:26: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-12 04:27:14 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-12 04:27:14 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gUcLbuhuUE/ea_profile.json
* 2023-06-12 04:27:15 (2259) [INFO] Backed up EA4 profile to /tmp/gUcLbuhuUE/ea_profile.json
* 2023-06-12 04:27:16 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-12 04:27:16 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-13 04:26:28 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-13 04:26:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-13 04:26:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-13 04:26:28 (4089) [INFO] 
* 2023-06-13 04:26:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-13 04:26:29 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-13 04:26:29 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-13 04:26:29 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-13 04:26:29 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-13 04:26:29 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-13 04:26:29 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-13 04:26:29 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-13 04:26:29 (4119) [INFO] 
* 2023-06-13 04:26:29 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-13 04:26:29 (4089) [INFO] 
* 2023-06-13 04:26:57 (4102) [INFO] 
* 2023-06-13 04:26:57 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-13 04:26:57 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-13 04:26:57 (4119) [INFO] 
* 2023-06-13 04:26:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-13 04:26:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-13 04:26:59 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-13 04:26:59 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-13 04:26:59 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-13 04:26:59 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-13 04:26: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-06-13 04:27:33 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-13 04:27:33 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V6SP7Rfa53/ea_profile.json
* 2023-06-13 04:27:34 (2259) [INFO] Backed up EA4 profile to /tmp/V6SP7Rfa53/ea_profile.json
* 2023-06-13 04:27:35 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-13 04:27:35 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-14 04:26:26 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-14 04:26:26 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-14 04:26:26 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-14 04:26:26 (4089) [INFO] 
* 2023-06-14 04:26:26 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-14 04:26:26 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-14 04:26:26 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-14 04:26:26 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-14 04:26:26 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-14 04:26:26 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-14 04:26:26 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-14 04:26:26 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-14 04:26:27 (4119) [INFO] 
* 2023-06-14 04:26:27 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-14 04:26:27 (4089) [INFO] 
* 2023-06-14 04:26:55 (4102) [INFO] 
* 2023-06-14 04:26:55 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-14 04:26:55 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-14 04:26:55 (4119) [INFO] 
* 2023-06-14 04:26:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-14 04:26:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-14 04:26:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-14 04:26:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-14 04:26:57 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-14 04:26:57 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-14 04:26: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-06-14 04:27:21 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-14 04:27:21 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/06SSwVr5n3/ea_profile.json
* 2023-06-14 04:27:22 (2259) [INFO] Backed up EA4 profile to /tmp/06SSwVr5n3/ea_profile.json
* 2023-06-14 04:27:23 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-14 04:27:23 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-15 04:27:54 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-15 04:27:54 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-15 04:27:54 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-15 04:27:54 (4089) [INFO] 
* 2023-06-15 04:27:55 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-15 04:27:55 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-15 04:27:55 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-15 04:27:55 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-15 04:27:55 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-15 04:27:55 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-15 04:27:55 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-15 04:27:55 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-15 04:27:55 (4119) [INFO] 
* 2023-06-15 04:27:55 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-15 04:27:55 (4089) [INFO] 
* 2023-06-15 04:28:22 (4102) [INFO] 
* 2023-06-15 04:28:22 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-15 04:28:22 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-15 04:28:22 (4119) [INFO] 
* 2023-06-15 04:28:22 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-15 04:28:22 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-15 04:28:24 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-15 04:28:24 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-15 04:28:24 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-15 04:28:24 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-15 04:28: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-15 04:28:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-15 04:28:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YL_u29j65R/ea_profile.json
* 2023-06-15 04:28:50 (2259) [INFO] Backed up EA4 profile to /tmp/YL_u29j65R/ea_profile.json
* 2023-06-15 04:28:50 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-15 04:28:51 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-16 04:26:28 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-16 04:26:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-16 04:26:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-16 04:26:28 (4089) [INFO] 
* 2023-06-16 04:26:29 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-16 04:26:29 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-16 04:26:29 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-16 04:26:29 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-16 04:26:29 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-16 04:26:29 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-16 04:26:29 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-16 04:26:29 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-16 04:26:29 (4119) [INFO] 
* 2023-06-16 04:26:29 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-16 04:26:29 (4089) [INFO] 
* 2023-06-16 04:27:08 (4102) [INFO] 
* 2023-06-16 04:27:08 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-16 04:27:08 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-16 04:27:08 (4119) [INFO] 
* 2023-06-16 04:27:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-16 04:27:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-16 04:27:10 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-16 04:27:10 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-16 04:27:10 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-16 04:27:10 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-16 04:27: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-06-16 04:27:36 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-16 04:27:36 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2FjmV1bQYZ/ea_profile.json
* 2023-06-16 04:27:37 (2259) [INFO] Backed up EA4 profile to /tmp/2FjmV1bQYZ/ea_profile.json
* 2023-06-16 04:27:38 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-16 04:27:38 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-17 04:27:27 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-17 04:27:27 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-17 04:27:27 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-17 04:27:27 (4089) [INFO] 
* 2023-06-17 04:27:27 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-17 04:27:27 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-17 04:27:27 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-17 04:27:27 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-17 04:27:27 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-17 04:27:27 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-17 04:27:27 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-17 04:27:27 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-17 04:27:27 (4119) [INFO] 
* 2023-06-17 04:27:27 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-17 04:27:27 (4089) [INFO] 
* 2023-06-17 04:28:03 (4102) [INFO] 
* 2023-06-17 04:28:03 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-17 04:28:03 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-17 04:28:03 (4119) [INFO] 
* 2023-06-17 04:28:03 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-17 04:28:03 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-17 04:28:06 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-17 04:28:06 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-17 04:28:06 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-17 04:28:06 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-17 04:28:06 (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 04:28:35 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-17 04:28:35 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/72l86XvePe/ea_profile.json
* 2023-06-17 04:28:36 (2259) [INFO] Backed up EA4 profile to /tmp/72l86XvePe/ea_profile.json
* 2023-06-17 04:28:37 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-17 04:28:37 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-18 04:27:21 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-18 04:27:21 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-18 04:27:21 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-18 04:27:21 (4089) [INFO] 
* 2023-06-18 04:27:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-18 04:27:22 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-18 04:27:22 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-18 04:27:22 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-18 04:27:22 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-18 04:27:22 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-18 04:27:22 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-18 04:27:22 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-18 04:27:22 (4119) [INFO] 
* 2023-06-18 04:27:22 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-18 04:27:22 (4089) [INFO] 
* 2023-06-18 04:27:58 (4102) [INFO] 
* 2023-06-18 04:27:58 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-18 04:27:58 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-18 04:27:58 (4119) [INFO] 
* 2023-06-18 04:27:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-18 04:27:58 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-18 04:28:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-18 04:28:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-18 04:28:02 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-18 04:28:02 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-18 04:28: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-18 04:28:29 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-18 04:28:29 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E3jCITD6DR/ea_profile.json
* 2023-06-18 04:28:30 (2259) [INFO] Backed up EA4 profile to /tmp/E3jCITD6DR/ea_profile.json
* 2023-06-18 04:28:31 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-18 04:28:31 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-19 04:26:30 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-19 04:26:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-19 04:26:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-19 04:26:30 (4089) [INFO] 
* 2023-06-19 04:26:30 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-19 04:26:30 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-19 04:26:30 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-19 04:26:30 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-19 04:26:30 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-19 04:26:30 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-19 04:26:30 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-19 04:26:31 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-19 04:26:31 (4119) [INFO] 
* 2023-06-19 04:26:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-19 04:26:31 (4089) [INFO] 
* 2023-06-19 04:27:08 (4102) [INFO] 
* 2023-06-19 04:27:08 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-19 04:27:08 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-19 04:27:08 (4119) [INFO] 
* 2023-06-19 04:27:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-19 04:27:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-19 04:27:10 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-19 04:27:10 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-19 04:27:10 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-19 04:27:10 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-19 04:27: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-06-19 04:27:42 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-19 04:27:42 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sRXlsc1KE3/ea_profile.json
* 2023-06-19 04:27:43 (2259) [INFO] Backed up EA4 profile to /tmp/sRXlsc1KE3/ea_profile.json
* 2023-06-19 04:27:44 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-19 04:27:44 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-20 04:26:22 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-20 04:26:22 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-20 04:26:22 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-20 04:26:22 (4089) [INFO] 
* 2023-06-20 04:26:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-20 04:26:23 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-20 04:26:23 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-20 04:26:23 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-20 04:26:23 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-20 04:26:23 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-20 04:26:23 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-20 04:26:23 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-20 04:26:23 (4119) [INFO] 
* 2023-06-20 04:26:23 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-20 04:26:23 (4089) [INFO] 
* 2023-06-20 04:26:49 (4102) [INFO] 
* 2023-06-20 04:26:49 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-20 04:26:49 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-20 04:26:49 (4119) [INFO] 
* 2023-06-20 04:26:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-20 04:26:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-20 04:26:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-20 04:26:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-20 04:26:51 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-20 04:26:51 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-20 04:26: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-20 04:27:15 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-20 04:27:15 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9Mdg9tZRUq/ea_profile.json
* 2023-06-20 04:27:16 (2259) [INFO] Backed up EA4 profile to /tmp/9Mdg9tZRUq/ea_profile.json
* 2023-06-20 04:27:16 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-20 04:27:16 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-21 04:26:31 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-21 04:26:31 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-21 04:26:31 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-21 04:26:31 (4089) [INFO] 
* 2023-06-21 04:26:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-21 04:26:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-21 04:26:31 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-21 04:26:31 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-21 04:26:31 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-21 04:26:31 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-21 04:26:31 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-21 04:26:31 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-21 04:26:31 (4119) [INFO] 
* 2023-06-21 04:26:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-21 04:26:31 (4089) [INFO] 
* 2023-06-21 04:27:08 (4102) [INFO] 
* 2023-06-21 04:27:08 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-21 04:27:08 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-21 04:27:08 (4119) [INFO] 
* 2023-06-21 04:27:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-21 04:27:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-21 04:27:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-21 04:27:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-21 04:27:11 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-21 04:27:11 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-21 04:27: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-21 04:27:38 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-21 04:27:38 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zi1eq24gu4/ea_profile.json
* 2023-06-21 04:27:38 (2259) [INFO] Backed up EA4 profile to /tmp/zi1eq24gu4/ea_profile.json
* 2023-06-21 04:27:39 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-21 04:27:39 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-22 04:26:38 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-22 04:26:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-22 04:26:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-22 04:26:38 (4089) [INFO] 
* 2023-06-22 04:26:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-22 04:26:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-22 04:26:38 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-22 04:26:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-22 04:26:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-22 04:26:38 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-22 04:26:38 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-22 04:26:39 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-22 04:26:39 (4119) [INFO] 
* 2023-06-22 04:26:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-22 04:26:39 (4089) [INFO] 
* 2023-06-22 04:27:17 (4102) [INFO] 
* 2023-06-22 04:27:17 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-22 04:27:17 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-22 04:27:17 (4119) [INFO] 
* 2023-06-22 04:27:17 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-22 04:27:17 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-22 04:27:20 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-22 04:27:20 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-22 04:27:20 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-22 04:27:20 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-22 04:27: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-06-22 04:27:48 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-22 04:27:48 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/v1N_08mGwH/ea_profile.json
* 2023-06-22 04:27:49 (2259) [INFO] Backed up EA4 profile to /tmp/v1N_08mGwH/ea_profile.json
* 2023-06-22 04:27:50 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-22 04:27:50 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-23 04:26:29 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-23 04:26:29 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-23 04:26:29 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-23 04:26:29 (4089) [INFO] 
* 2023-06-23 04:26:29 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-23 04:26:30 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-23 04:26:30 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-23 04:26:30 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-23 04:26:30 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-23 04:26:30 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-23 04:26:30 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-23 04:26:30 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-23 04:26:30 (4119) [INFO] 
* 2023-06-23 04:26:30 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-23 04:26:30 (4089) [INFO] 
* 2023-06-23 04:27:09 (4102) [INFO] 
* 2023-06-23 04:27:09 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-23 04:27:09 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-23 04:27:09 (4119) [INFO] 
* 2023-06-23 04:27:09 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-23 04:27:09 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-23 04:27:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-23 04:27:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-23 04:27:11 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-23 04:27:11 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-23 04:27: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-23 04:27:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-23 04:27:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5uJFrUSexX/ea_profile.json
* 2023-06-23 04:27:38 (2259) [INFO] Backed up EA4 profile to /tmp/5uJFrUSexX/ea_profile.json
* 2023-06-23 04:27:39 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-23 04:27:39 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-24 04:27:23 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-24 04:27:23 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-24 04:27:23 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-24 04:27:23 (4089) [INFO] 
* 2023-06-24 04:27:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-24 04:27:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-24 04:27:24 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-24 04:27:24 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-24 04:27:24 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-24 04:27:24 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-24 04:27:24 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-24 04:27:24 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-24 04:27:24 (4119) [INFO] 
* 2023-06-24 04:27:24 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-24 04:27:24 (4089) [INFO] 
* 2023-06-24 04:27:55 (4102) [INFO] 
* 2023-06-24 04:27:55 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-24 04:27:55 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-24 04:27:55 (4119) [INFO] 
* 2023-06-24 04:27:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-24 04:27:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-24 04:27:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-24 04:27:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-24 04:27:57 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-24 04:27:57 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-24 04:27: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-06-24 04:28:21 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-24 04:28:21 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dHYoJdzR1J/ea_profile.json
* 2023-06-24 04:28:22 (2259) [INFO] Backed up EA4 profile to /tmp/dHYoJdzR1J/ea_profile.json
* 2023-06-24 04:28:23 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-24 04:28:23 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-25 04:27:28 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-25 04:27:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-25 04:27:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-25 04:27:28 (4089) [INFO] 
* 2023-06-25 04:27:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-25 04:27:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-25 04:27:28 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-25 04:27:28 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-25 04:27:28 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-25 04:27:28 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-25 04:27:28 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-25 04:27:29 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-25 04:27:29 (4119) [INFO] 
* 2023-06-25 04:27:29 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-25 04:27:29 (4089) [INFO] 
* 2023-06-25 04:28:07 (4102) [INFO] 
* 2023-06-25 04:28:07 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-25 04:28:07 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-25 04:28:08 (4119) [INFO] 
* 2023-06-25 04:28:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-25 04:28:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-25 04:28:10 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-25 04:28:10 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-25 04:28:10 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-25 04:28:10 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-25 04:28: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-06-25 04:28:38 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-25 04:28:38 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZIWkiFAl66/ea_profile.json
* 2023-06-25 04:28:39 (2259) [INFO] Backed up EA4 profile to /tmp/ZIWkiFAl66/ea_profile.json
* 2023-06-25 04:28:40 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-25 04:28:40 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-26 04:26:31 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-26 04:26:31 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-26 04:26:31 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-26 04:26:31 (4089) [INFO] 
* 2023-06-26 04:26:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-26 04:26:32 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-26 04:26:32 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-26 04:26:32 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-26 04:26:32 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-26 04:26:32 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-26 04:26:32 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-26 04:26:32 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-26 04:26:32 (4119) [INFO] 
* 2023-06-26 04:26:32 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-26 04:26:32 (4089) [INFO] 
* 2023-06-26 04:27:14 (4102) [INFO] 
* 2023-06-26 04:27:14 (4102) [INFO] kernel.x86_64                     3.10.0-1160.90.1.el7                   updates
* 2023-06-26 04:27:14 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-26 04:27:14 (4119) [INFO] 
* 2023-06-26 04:27:14 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-26 04:27:14 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-26 04:27:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-26 04:27:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-26 04:27:16 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-26 04:27:16 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-26 04:27:16 (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 04:27:42 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-26 04:27:42 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/v4xy3Bwjok/ea_profile.json
* 2023-06-26 04:27:43 (2259) [INFO] Backed up EA4 profile to /tmp/v4xy3Bwjok/ea_profile.json
* 2023-06-26 04:27:43 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-26 04:27:44 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-27 04:27:01 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-27 04:27:01 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-27 04:27:01 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-27 04:27:01 (4089) [INFO] 
* 2023-06-27 04:27:01 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-27 04:27:01 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-27 04:27:01 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-27 04:27:01 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-27 04:27:01 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-27 04:27:01 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-27 04:27:01 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-27 04:27:02 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-27 04:27:02 (4119) [INFO] 
* 2023-06-27 04:27:02 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-27 04:27:02 (4089) [INFO] 
* 2023-06-27 04:27:40 (4102) [INFO] 
* 2023-06-27 04:27:40 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-06-27 04:27:40 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-27 04:27:40 (4119) [INFO] 
* 2023-06-27 04:27:40 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-27 04:27:40 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-27 04:27:42 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-27 04:27:42 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-27 04:27:42 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-27 04:27:42 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-27 04:27: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-27 04:28:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-27 04:28:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zcjyqKItyY/ea_profile.json
* 2023-06-27 04:28:11 (2259) [INFO] Backed up EA4 profile to /tmp/zcjyqKItyY/ea_profile.json
* 2023-06-27 04:28:12 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-27 04:28:12 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-28 04:26:34 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-28 04:26:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-28 04:26:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-28 04:26:34 (4089) [INFO] 
* 2023-06-28 04:26:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-28 04:26:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-28 04:26:34 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-28 04:26:34 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-28 04:26:34 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-28 04:26:34 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-28 04:26:34 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-28 04:26:35 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-28 04:26:35 (4119) [INFO] 
* 2023-06-28 04:26:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-28 04:26:35 (4089) [INFO] 
* 2023-06-28 04:27:15 (4102) [INFO] 
* 2023-06-28 04:27:15 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-06-28 04:27:15 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-28 04:27:15 (4119) [INFO] 
* 2023-06-28 04:27:15 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-28 04:27:15 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-28 04:27:17 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-28 04:27:17 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-28 04:27:17 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-28 04:27:17 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-28 04:27: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-28 04:27:43 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-28 04:27:43 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bt7xdjZyRV/ea_profile.json
* 2023-06-28 04:27:44 (2259) [INFO] Backed up EA4 profile to /tmp/bt7xdjZyRV/ea_profile.json
* 2023-06-28 04:27:44 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-28 04:27:44 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-29 04:27:08 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-29 04:27:08 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-29 04:27:08 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-29 04:27:08 (4089) [INFO] 
* 2023-06-29 04:27:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-29 04:27:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-29 04:27:08 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-29 04:27:08 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-29 04:27:08 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-29 04:27:08 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-29 04:27:08 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-29 04:27:09 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-29 04:27:09 (4119) [INFO] 
* 2023-06-29 04:27:09 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-29 04:27:09 (4089) [INFO] 
* 2023-06-29 04:27:48 (4102) [INFO] 
* 2023-06-29 04:27:48 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-06-29 04:27:48 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-29 04:27:49 (4119) [INFO] 
* 2023-06-29 04:27:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-29 04:27:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-29 04:27:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-29 04:27:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-29 04:27:51 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-29 04:27:51 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-29 04:27: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-29 04:28:17 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-29 04:28:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/53i_CX1tFh/ea_profile.json
* 2023-06-29 04:28:18 (2259) [INFO] Backed up EA4 profile to /tmp/53i_CX1tFh/ea_profile.json
* 2023-06-29 04:28:19 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-29 04:28:19 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-30 04:26:49 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-06-30 04:26:49 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-30 04:26:49 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-30 04:26:49 (4089) [INFO] 
* 2023-06-30 04:26:49 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-30 04:26:50 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-06-30 04:26:50 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-30 04:26:50 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-30 04:26:50 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-30 04:26:50 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-06-30 04:26:50 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-06-30 04:26:50 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-06-30 04:26:50 (4119) [INFO] 
* 2023-06-30 04:26:50 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-30 04:26:50 (4089) [INFO] 
* 2023-06-30 04:27:28 (4102) [INFO] 
* 2023-06-30 04:27:28 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-06-30 04:27:28 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-06-30 04:27:28 (4119) [INFO] 
* 2023-06-30 04:27:28 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-30 04:27:28 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-30 04:27:31 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-06-30 04:27:31 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-06-30 04:27:31 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-06-30 04:27:31 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-06-30 04:27: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-06-30 04:27:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-30 04:27:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BNo9mHvboy/ea_profile.json
* 2023-06-30 04:28:00 (2259) [INFO] Backed up EA4 profile to /tmp/BNo9mHvboy/ea_profile.json
* 2023-06-30 04:28:01 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-06-30 04:28:01 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-01 04:27:26 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-01 04:27:26 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-01 04:27:26 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-01 04:27:26 (4089) [INFO] 
* 2023-07-01 04:27:27 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-01 04:27:27 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-01 04:27:27 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-01 04:27:27 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-01 04:27:27 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-01 04:27:27 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-01 04:27:27 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-01 04:27:27 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-01 04:27:27 (4119) [INFO] 
* 2023-07-01 04:27:27 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-01 04:27:27 (4089) [INFO] 
* 2023-07-01 04:28:07 (4102) [INFO] 
* 2023-07-01 04:28:07 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-01 04:28:07 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-01 04:28:07 (4119) [INFO] 
* 2023-07-01 04:28:07 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-01 04:28:07 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-01 04:28:09 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-01 04:28:09 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-01 04:28:09 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-01 04:28:09 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-01 04:28:09 (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 04:28:36 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-01 04:28:36 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wnJs_h2xFH/ea_profile.json
* 2023-07-01 04:28:37 (2259) [INFO] Backed up EA4 profile to /tmp/wnJs_h2xFH/ea_profile.json
* 2023-07-01 04:28:37 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-01 04:28:37 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-02 04:27:28 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-02 04:27:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-02 04:27:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-02 04:27:28 (4089) [INFO] 
* 2023-07-02 04:27:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-02 04:27:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-02 04:27:28 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-02 04:27:28 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-02 04:27:28 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-02 04:27:28 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-02 04:27:28 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-02 04:27:28 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-02 04:27:29 (4119) [INFO] 
* 2023-07-02 04:27:29 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-02 04:27:29 (4089) [INFO] 
* 2023-07-02 04:28:11 (4102) [INFO] 
* 2023-07-02 04:28:11 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-02 04:28:11 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-02 04:28:11 (4119) [INFO] 
* 2023-07-02 04:28:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-02 04:28:11 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-02 04:28:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-02 04:28:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-02 04:28:15 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-02 04:28:15 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-02 04:28: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-07-02 04:28:40 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-02 04:28:40 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qoi2G5Lclc/ea_profile.json
* 2023-07-02 04:28:41 (2259) [INFO] Backed up EA4 profile to /tmp/qoi2G5Lclc/ea_profile.json
* 2023-07-02 04:28:41 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-02 04:28:41 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-03 04:26:33 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-03 04:26:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-03 04:26:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-03 04:26:33 (4089) [INFO] 
* 2023-07-03 04:26:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-03 04:26:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-03 04:26:33 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-03 04:26:33 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-03 04:26:33 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-03 04:26:33 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-03 04:26:33 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-03 04:26:34 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-03 04:26:34 (4119) [INFO] 
* 2023-07-03 04:26:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-03 04:26:34 (4089) [INFO] 
* 2023-07-03 04:27:16 (4102) [INFO] 
* 2023-07-03 04:27:16 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-03 04:27:16 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-03 04:27:17 (4119) [INFO] 
* 2023-07-03 04:27:17 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-03 04:27:17 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-03 04:27:19 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-03 04:27:19 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-03 04:27:19 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-03 04:27:19 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-03 04:27:19 (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 04:27:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-03 04:27:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/98C7ezE2yk/ea_profile.json
* 2023-07-03 04:27:45 (2259) [INFO] Backed up EA4 profile to /tmp/98C7ezE2yk/ea_profile.json
* 2023-07-03 04:27:45 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-03 04:27:45 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-04 04:26:25 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-04 04:26:25 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-04 04:26:25 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-04 04:26:25 (4089) [INFO] 
* 2023-07-04 04:26:25 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-04 04:26:26 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-04 04:26:26 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-04 04:26:26 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-04 04:26:26 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-04 04:26:26 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-04 04:26:26 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-04 04:26:26 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-04 04:26:26 (4119) [INFO] 
* 2023-07-04 04:26:26 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-04 04:26:26 (4089) [INFO] 
* 2023-07-04 04:26:56 (4102) [INFO] 
* 2023-07-04 04:26:56 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-04 04:26:56 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-04 04:26:56 (4119) [INFO] 
* 2023-07-04 04:26:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-04 04:26:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-04 04:26:58 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-04 04:26:58 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-04 04:26:58 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-04 04:26:58 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-04 04:26: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-04 04:27:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-04 04:27:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F4q0GPatln/ea_profile.json
* 2023-07-04 04:27:25 (2259) [INFO] Backed up EA4 profile to /tmp/F4q0GPatln/ea_profile.json
* 2023-07-04 04:27:25 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-04 04:27:25 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-05 04:26:28 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-05 04:26:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-05 04:26:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-05 04:26:28 (4089) [INFO] 
* 2023-07-05 04:26:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-05 04:26:29 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-05 04:26:29 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-05 04:26:29 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-05 04:26:29 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-05 04:26:29 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-05 04:26:29 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-05 04:26:29 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-05 04:26:29 (4119) [INFO] 
* 2023-07-05 04:26:29 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-05 04:26:29 (4089) [INFO] 
* 2023-07-05 04:27:06 (4102) [INFO] 
* 2023-07-05 04:27:06 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-05 04:27:06 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-05 04:27:06 (4119) [INFO] 
* 2023-07-05 04:27:06 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-05 04:27:06 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-05 04:27:09 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-05 04:27:09 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-05 04:27:09 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-05 04:27:09 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-05 04:27:09 (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 04:27:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-05 04:27:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yjelvrvmfr/ea_profile.json
* 2023-07-05 04:27:38 (2259) [INFO] Backed up EA4 profile to /tmp/yjelvrvmfr/ea_profile.json
* 2023-07-05 04:27:38 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-05 04:27:38 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-06 04:26:30 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-06 04:26:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-06 04:26:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-06 04:26:30 (4089) [INFO] 
* 2023-07-06 04:26:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-06 04:26:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-06 04:26:31 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-06 04:26:31 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-06 04:26:31 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-06 04:26:31 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-06 04:26:31 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-06 04:26:31 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-06 04:26:31 (4119) [INFO] 
* 2023-07-06 04:26:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-06 04:26:31 (4089) [INFO] 
* 2023-07-06 04:27:11 (4102) [INFO] 
* 2023-07-06 04:27:11 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-06 04:27:11 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-06 04:27:11 (4119) [INFO] 
* 2023-07-06 04:27:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-06 04:27:11 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-06 04:27:13 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-06 04:27:13 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-06 04:27:13 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-06 04:27:13 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-06 04:27: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-07-06 04:27:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-06 04:27:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ie4JGBxuPJ/ea_profile.json
* 2023-07-06 04:27:40 (2259) [INFO] Backed up EA4 profile to /tmp/Ie4JGBxuPJ/ea_profile.json
* 2023-07-06 04:27:41 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-06 04:27:41 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-07 04:26:41 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-07 04:26:41 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-07 04:26:41 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-07 04:26:41 (4089) [INFO] 
* 2023-07-07 04:26:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-07 04:26:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-07 04:26:41 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-07 04:26:41 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-07 04:26:41 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-07 04:26:41 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-07 04:26:41 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-07 04:26:42 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-07 04:26:42 (4119) [INFO] 
* 2023-07-07 04:26:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-07 04:26:42 (4089) [INFO] 
* 2023-07-07 04:27:20 (4102) [INFO] 
* 2023-07-07 04:27:20 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-07 04:27:20 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-07 04:27:20 (4119) [INFO] 
* 2023-07-07 04:27:20 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-07 04:27:20 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-07 04:27:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-07 04:27:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-07 04:27:23 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-07 04:27:23 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-07 04:27: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-07-07 04:27:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-07 04:27:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ERMFptFHP8/ea_profile.json
* 2023-07-07 04:27:50 (2259) [INFO] Backed up EA4 profile to /tmp/ERMFptFHP8/ea_profile.json
* 2023-07-07 04:27:51 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-07 04:27:51 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-08 04:27:23 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-08 04:27:23 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-08 04:27:23 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-08 04:27:23 (4089) [INFO] 
* 2023-07-08 04:27:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-08 04:27:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-08 04:27:24 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-08 04:27:24 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-08 04:27:24 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-08 04:27:24 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-08 04:27:24 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-08 04:27:25 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-08 04:27:25 (4119) [INFO] 
* 2023-07-08 04:27:25 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-08 04:27:25 (4089) [INFO] 
* 2023-07-08 04:28:01 (4102) [INFO] 
* 2023-07-08 04:28:01 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-08 04:28:01 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-08 04:28:01 (4119) [INFO] 
* 2023-07-08 04:28:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-08 04:28:01 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-08 04:28:05 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-08 04:28:05 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-08 04:28:05 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-08 04:28:05 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-08 04:28: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-07-08 04:28:30 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-08 04:28:30 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nWH4ev7w8I/ea_profile.json
* 2023-07-08 04:28:31 (2259) [INFO] Backed up EA4 profile to /tmp/nWH4ev7w8I/ea_profile.json
* 2023-07-08 04:28:32 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-08 04:28:32 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-09 04:27:24 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-09 04:27:24 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-09 04:27:24 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-09 04:27:24 (4089) [INFO] 
* 2023-07-09 04:27:25 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-09 04:27:25 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-09 04:27:25 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-09 04:27:25 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-09 04:27:25 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-09 04:27:25 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-09 04:27:25 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-09 04:27:25 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-09 04:27:25 (4119) [INFO] 
* 2023-07-09 04:27:25 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-09 04:27:25 (4089) [INFO] 
* 2023-07-09 04:28:05 (4102) [INFO] 
* 2023-07-09 04:28:05 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-09 04:28:05 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-09 04:28:05 (4119) [INFO] 
* 2023-07-09 04:28:05 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-09 04:28:05 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-09 04:28:08 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-09 04:28:08 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-09 04:28:08 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-09 04:28:08 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-09 04:28:08 (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 04:28:35 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-09 04:28:35 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DMps4UgF3E/ea_profile.json
* 2023-07-09 04:28:36 (2259) [INFO] Backed up EA4 profile to /tmp/DMps4UgF3E/ea_profile.json
* 2023-07-09 04:28:37 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-09 04:28:37 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-10 04:26:30 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-10 04:26:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-10 04:26:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-10 04:26:30 (4089) [INFO] 
* 2023-07-10 04:26:30 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-10 04:26:30 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-10 04:26:30 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-10 04:26:30 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-10 04:26:30 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-10 04:26:30 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-10 04:26:30 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-10 04:26:30 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-10 04:26:31 (4119) [INFO] 
* 2023-07-10 04:26:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-10 04:26:31 (4089) [INFO] 
* 2023-07-10 04:27:09 (4102) [INFO] 
* 2023-07-10 04:27:09 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-10 04:27:09 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-10 04:27:09 (4119) [INFO] 
* 2023-07-10 04:27:09 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-10 04:27:09 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-10 04:27:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-10 04:27:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-10 04:27:11 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-10 04:27:11 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-10 04:27: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-07-10 04:27:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-10 04:27:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/18WjlcYtL5/ea_profile.json
* 2023-07-10 04:27:40 (2259) [INFO] Backed up EA4 profile to /tmp/18WjlcYtL5/ea_profile.json
* 2023-07-10 04:27:40 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-10 04:27:40 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-11 04:26:31 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-11 04:26:31 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-11 04:26:31 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-11 04:26:31 (4089) [INFO] 
* 2023-07-11 04:26:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-11 04:26:32 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-11 04:26:32 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-11 04:26:32 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-11 04:26:32 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-11 04:26:32 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-11 04:26:32 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-11 04:26:32 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-11 04:26:32 (4119) [INFO] 
* 2023-07-11 04:26:32 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-11 04:26:32 (4089) [INFO] 
* 2023-07-11 04:27:11 (4102) [INFO] 
* 2023-07-11 04:27:11 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-11 04:27:11 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-11 04:27:11 (4119) [INFO] 
* 2023-07-11 04:27:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-11 04:27:11 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-11 04:27:14 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-11 04:27:14 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-11 04:27:14 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-11 04:27:14 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-11 04:27:14 (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 04:27:41 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-11 04:27:41 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ouTaHTO4UJ/ea_profile.json
* 2023-07-11 04:27:42 (2259) [INFO] Backed up EA4 profile to /tmp/ouTaHTO4UJ/ea_profile.json
* 2023-07-11 04:27:42 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-11 04:27:42 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-12 04:26:43 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-12 04:26:43 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-12 04:26:43 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-12 04:26:43 (4089) [INFO] 
* 2023-07-12 04:26:44 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-12 04:26:44 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-12 04:26:44 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-12 04:26:44 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-12 04:26:44 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-12 04:26:44 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-12 04:26:44 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-12 04:26:44 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-12 04:26:44 (4119) [INFO] 
* 2023-07-12 04:26:44 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-12 04:26:44 (4089) [INFO] 
* 2023-07-12 04:27:23 (4102) [INFO] 
* 2023-07-12 04:27:23 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-12 04:27:23 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-12 04:27:23 (4119) [INFO] 
* 2023-07-12 04:27:23 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-12 04:27:23 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-12 04:27:25 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-12 04:27:25 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-12 04:27:25 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-12 04:27:25 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-12 04:27: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-07-12 04:27:51 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-12 04:27:51 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bu9RZaNHzp/ea_profile.json
* 2023-07-12 04:27:52 (2259) [INFO] Backed up EA4 profile to /tmp/bu9RZaNHzp/ea_profile.json
* 2023-07-12 04:27:53 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-12 04:27:53 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-13 04:29:28 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-13 04:29:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-13 04:29:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-13 04:29:28 (4089) [INFO] 
* 2023-07-13 04:29:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-13 04:29:29 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-13 04:29:29 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-13 04:29:29 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-13 04:29:29 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-13 04:29:29 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-13 04:29:29 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-13 04:29:29 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-13 04:29:29 (4119) [INFO] 
* 2023-07-13 04:29:29 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-13 04:29:29 (4089) [INFO] 
* 2023-07-13 04:30:14 (4102) [INFO] 
* 2023-07-13 04:30:14 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-13 04:30:14 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-13 04:30:14 (4119) [INFO] 
* 2023-07-13 04:30:14 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-13 04:30:14 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-13 04:30:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-13 04:30:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-13 04:30:16 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-13 04:30:16 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-13 04:30:16 (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 04:30:42 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-13 04:30:42 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jVa6KAqGTd/ea_profile.json
* 2023-07-13 04:30:43 (2259) [INFO] Backed up EA4 profile to /tmp/jVa6KAqGTd/ea_profile.json
* 2023-07-13 04:30:44 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-13 04:30:44 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-14 04:27:10 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-14 04:27:10 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-14 04:27:10 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-14 04:27:10 (4089) [INFO] 
* 2023-07-14 04:27:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-14 04:27:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-14 04:27:10 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-14 04:27:10 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-14 04:27:10 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-14 04:27:10 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-14 04:27:10 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-14 04:27:10 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-14 04:27:11 (4119) [INFO] 
* 2023-07-14 04:27:11 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-14 04:27:11 (4089) [INFO] 
* 2023-07-14 04:27:48 (4102) [INFO] 
* 2023-07-14 04:27:48 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-14 04:27:48 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-14 04:27:48 (4119) [INFO] 
* 2023-07-14 04:27:48 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-14 04:27:48 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-14 04:27:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-14 04:27:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-14 04:27:51 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-14 04:27:51 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-14 04:27: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-07-14 04:28:17 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-14 04:28:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jiZu9CjfiF/ea_profile.json
* 2023-07-14 04:28:18 (2259) [INFO] Backed up EA4 profile to /tmp/jiZu9CjfiF/ea_profile.json
* 2023-07-14 04:28:19 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-14 04:28:19 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-15 04:27:25 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-15 04:27:25 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-15 04:27:25 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-15 04:27:25 (4089) [INFO] 
* 2023-07-15 04:27:25 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-15 04:27:25 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-15 04:27:25 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-15 04:27:25 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-15 04:27:25 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-15 04:27:25 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-15 04:27:25 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-15 04:27:26 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-15 04:27:26 (4119) [INFO] 
* 2023-07-15 04:27:26 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-15 04:27:26 (4089) [INFO] 
* 2023-07-15 04:27:59 (4102) [INFO] 
* 2023-07-15 04:27:59 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-15 04:27:59 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-15 04:27:59 (4119) [INFO] 
* 2023-07-15 04:27:59 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-15 04:27:59 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-15 04:28:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-15 04:28:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-15 04:28:02 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-15 04:28:02 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-15 04:28: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-15 04:28:28 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-15 04:28:28 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FsTiMBt9s9/ea_profile.json
* 2023-07-15 04:28:29 (2259) [INFO] Backed up EA4 profile to /tmp/FsTiMBt9s9/ea_profile.json
* 2023-07-15 04:28:29 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-15 04:28:29 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-16 04:27:22 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-16 04:27:22 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-16 04:27:22 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-16 04:27:22 (4089) [INFO] 
* 2023-07-16 04:27:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-16 04:27:22 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-16 04:27:22 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-16 04:27:22 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-16 04:27:22 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-16 04:27:22 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-16 04:27:22 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-16 04:27:23 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-16 04:27:23 (4119) [INFO] 
* 2023-07-16 04:27:23 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-16 04:27:23 (4089) [INFO] 
* 2023-07-16 04:27:58 (4102) [INFO] 
* 2023-07-16 04:27:58 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-16 04:27:58 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-16 04:27:58 (4119) [INFO] 
* 2023-07-16 04:27:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-16 04:27:58 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-16 04:28:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-16 04:28:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-16 04:28:02 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-16 04:28:02 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-16 04:28: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-16 04:28:28 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-16 04:28:28 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lzVuAseqzD/ea_profile.json
* 2023-07-16 04:28:29 (2259) [INFO] Backed up EA4 profile to /tmp/lzVuAseqzD/ea_profile.json
* 2023-07-16 04:28:29 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-16 04:28:29 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-17 04:26:36 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-17 04:26:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-17 04:26:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-17 04:26:36 (4089) [INFO] 
* 2023-07-17 04:26:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-17 04:26:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-17 04:26:36 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-17 04:26:36 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-17 04:26:36 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-17 04:26:36 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-17 04:26:36 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-17 04:26:36 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-17 04:26:36 (4119) [INFO] 
* 2023-07-17 04:26:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-17 04:26:36 (4089) [INFO] 
* 2023-07-17 04:27:12 (4102) [INFO] 
* 2023-07-17 04:27:12 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-17 04:27:12 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-17 04:27:12 (4119) [INFO] 
* 2023-07-17 04:27:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-17 04:27:12 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-17 04:27:14 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-17 04:27:14 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-17 04:27:14 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-17 04:27:14 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-17 04:27:14 (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 04:27:40 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-17 04:27:40 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/whsJl1S0U6/ea_profile.json
* 2023-07-17 04:27:41 (2259) [INFO] Backed up EA4 profile to /tmp/whsJl1S0U6/ea_profile.json
* 2023-07-17 04:27:42 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-17 04:27:42 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-18 04:27:47 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-18 04:27:47 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-18 04:27:47 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-18 04:27:47 (4089) [INFO] 
* 2023-07-18 04:27:47 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-18 04:27:48 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-18 04:27:48 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-18 04:27:48 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-18 04:27:48 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-18 04:27:48 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-18 04:27:48 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-18 04:27:49 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-18 04:27:49 (4119) [INFO] 
* 2023-07-18 04:27:49 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-18 04:27:49 (4089) [INFO] 
* 2023-07-18 04:28:46 (4102) [INFO] 
* 2023-07-18 04:28:46 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-18 04:28:46 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-18 04:28:46 (4119) [INFO] 
* 2023-07-18 04:28:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-18 04:28:46 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-18 04:28:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-18 04:28:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-18 04:28:57 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-18 04:28:57 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-18 04:28: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-18 04:29:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-18 04:29:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RnVA1JOnZF/ea_profile.json
* 2023-07-18 04:29:46 (2259) [INFO] Backed up EA4 profile to /tmp/RnVA1JOnZF/ea_profile.json
* 2023-07-18 04:29:47 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-18 04:29:47 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-19 04:28:00 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-19 04:28:00 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-19 04:28:00 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-19 04:28:00 (4089) [INFO] 
* 2023-07-19 04:28:01 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-19 04:28:02 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-19 04:28:02 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-19 04:28:02 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-19 04:28:02 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-19 04:28:02 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-19 04:28:02 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-19 04:28:03 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-19 04:28:03 (4119) [INFO] 
* 2023-07-19 04:28:03 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-19 04:28:03 (4089) [INFO] 
* 2023-07-19 04:29:08 (4102) [INFO] 
* 2023-07-19 04:29:08 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-19 04:29:08 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-19 04:29:08 (4119) [INFO] 
* 2023-07-19 04:29:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-19 04:29:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-19 04:29:21 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-19 04:29:21 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-19 04:29:21 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-19 04:29:21 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-19 04:29:21 (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 04:30:13 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-19 04:30:13 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1aPfrHyxyu/ea_profile.json
* 2023-07-19 04:30:15 (2259) [INFO] Backed up EA4 profile to /tmp/1aPfrHyxyu/ea_profile.json
* 2023-07-19 04:30:16 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-19 04:30:16 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-20 04:30:18 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2023-07-20 04:30:19 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-20 04:30:19 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-20 04:30:19 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-20 04:30:19 (4089) [INFO] 
* 2023-07-20 04:30:20 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-20 04:30:20 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-20 04:30:20 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-20 04:30:20 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-20 04:30:20 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-20 04:30:20 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-20 04:30:20 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-20 04:30:20 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-20 04:30:21 (4119) [INFO] 
* 2023-07-20 04:30:21 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-20 04:30:21 (4089) [INFO] 
* 2023-07-20 04:31:13 (4102) [INFO] 
* 2023-07-20 04:31:13 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-20 04:31:13 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-20 04:31:13 (4119) [INFO] 
* 2023-07-20 04:31:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-20 04:31:13 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-20 04:31:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-20 04:31:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-20 04:31:23 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-20 04:31:23 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-20 04:31: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-07-20 04:32:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-20 04:32:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fO9B2GzcFm/ea_profile.json
* 2023-07-20 04:32:12 (2259) [INFO] Backed up EA4 profile to /tmp/fO9B2GzcFm/ea_profile.json
* 2023-07-20 04:32:13 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-20 04:32:14 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-21 04:26:35 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-21 04:26:35 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-21 04:26:35 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-21 04:26:35 (4089) [INFO] 
* 2023-07-21 04:26:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-21 04:26:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-21 04:26:35 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-21 04:26:35 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-21 04:26:35 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-21 04:26:35 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-21 04:26:35 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-21 04:26:36 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-21 04:26:36 (4119) [INFO] 
* 2023-07-21 04:26:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-21 04:26:36 (4089) [INFO] 
* 2023-07-21 04:27:19 (4102) [INFO] 
* 2023-07-21 04:27:19 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-21 04:27:19 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-21 04:27:19 (4119) [INFO] 
* 2023-07-21 04:27:19 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-21 04:27:19 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-21 04:27:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-21 04:27:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-21 04:27:23 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-21 04:27:23 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-21 04:27: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-07-21 04:27:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-21 04:27:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0_O5cy5Ajo/ea_profile.json
* 2023-07-21 04:27:48 (2259) [INFO] Backed up EA4 profile to /tmp/0_O5cy5Ajo/ea_profile.json
* 2023-07-21 04:27:49 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-21 04:27:49 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-22 04:27:27 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-22 04:27:27 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-22 04:27:27 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-22 04:27:27 (4089) [INFO] 
* 2023-07-22 04:27:27 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-22 04:27:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-22 04:27:28 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-22 04:27:28 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-22 04:27:28 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-22 04:27:28 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-22 04:27:28 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-22 04:27:28 (4102) [INFO] Other repos take up 3.5 M of disk space (use --verbose for details)
* 2023-07-22 04:27:28 (4119) [INFO] 
* 2023-07-22 04:27:28 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-22 04:27:28 (4089) [INFO] 
* 2023-07-22 04:28:08 (4102) [INFO] 
* 2023-07-22 04:28:08 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-22 04:28:08 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-22 04:28:08 (4119) [INFO] 
* 2023-07-22 04:28:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-22 04:28:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-22 04:28:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-22 04:28:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-22 04:28:11 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-22 04:28:11 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-22 04:28: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-07-22 04:28:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-22 04:28:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ft9c80gc71/ea_profile.json
* 2023-07-22 04:28:38 (2259) [INFO] Backed up EA4 profile to /tmp/ft9c80gc71/ea_profile.json
* 2023-07-22 04:28:38 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-22 04:28:38 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-23 04:27:37 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-23 04:27:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-23 04:27:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-23 04:27:37 (4089) [INFO] 
* 2023-07-23 04:27:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-23 04:27:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-23 04:27:38 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-23 04:27:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-23 04:27:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-23 04:27:38 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-23 04:27:38 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-23 04:27:38 (4102) [INFO] Other repos take up 3.5 M of disk space (use --verbose for details)
* 2023-07-23 04:27:38 (4119) [INFO] 
* 2023-07-23 04:27:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-23 04:27:38 (4089) [INFO] 
* 2023-07-23 04:28:21 (4102) [INFO] 
* 2023-07-23 04:28:21 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-23 04:28:21 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-23 04:28:21 (4119) [INFO] 
* 2023-07-23 04:28:21 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-23 04:28:21 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-23 04:28:24 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-23 04:28:24 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-23 04:28:24 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-23 04:28:24 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-23 04:28: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-07-23 04:28:51 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-23 04:28:51 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GCK9dLgvFV/ea_profile.json
* 2023-07-23 04:28:52 (2259) [INFO] Backed up EA4 profile to /tmp/GCK9dLgvFV/ea_profile.json
* 2023-07-23 04:28:52 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-23 04:28:52 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-24 04:26:37 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-24 04:26:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-24 04:26:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-24 04:26:37 (4089) [INFO] 
* 2023-07-24 04:26:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-24 04:26:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-24 04:26:38 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-24 04:26:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-24 04:26:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-24 04:26:38 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-24 04:26:38 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-24 04:26:38 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-24 04:26:38 (4119) [INFO] 
* 2023-07-24 04:26:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-24 04:26:38 (4089) [INFO] 
* 2023-07-24 04:27:19 (4102) [INFO] 
* 2023-07-24 04:27:19 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-24 04:27:19 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-24 04:27:19 (4119) [INFO] 
* 2023-07-24 04:27:19 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-24 04:27:19 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-24 04:27:21 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-24 04:27:21 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-24 04:27:21 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-24 04:27:21 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-24 04:27:21 (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 04:27:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-24 04:27:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YK8vis2KFg/ea_profile.json
* 2023-07-24 04:27:48 (2259) [INFO] Backed up EA4 profile to /tmp/YK8vis2KFg/ea_profile.json
* 2023-07-24 04:27:49 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-24 04:27:49 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-25 04:26:37 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-25 04:26:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-25 04:26:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-25 04:26:37 (4089) [INFO] 
* 2023-07-25 04:26:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-25 04:26:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-25 04:26:38 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-25 04:26:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-25 04:26:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-25 04:26:38 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-25 04:26:38 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-25 04:26:38 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-25 04:26:38 (4119) [INFO] 
* 2023-07-25 04:26:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-25 04:26:38 (4089) [INFO] 
* 2023-07-25 04:27:19 (4102) [INFO] 
* 2023-07-25 04:27:19 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-25 04:27:19 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-25 04:27:19 (4119) [INFO] 
* 2023-07-25 04:27:19 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-25 04:27:19 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-25 04:27:22 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-25 04:27:22 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-25 04:27:22 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-25 04:27:22 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-25 04:27:22 (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 04:27:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-25 04:27:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cje4bguxZe/ea_profile.json
* 2023-07-25 04:27:51 (2259) [INFO] Backed up EA4 profile to /tmp/cje4bguxZe/ea_profile.json
* 2023-07-25 04:27:52 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-25 04:27:52 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-26 04:26:41 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-26 04:26:41 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-26 04:26:41 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-26 04:26:41 (4089) [INFO] 
* 2023-07-26 04:26:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-26 04:26:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-26 04:26:42 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-26 04:26:42 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-26 04:26:42 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-26 04:26:42 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-26 04:26:42 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-26 04:26:42 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-26 04:26:42 (4119) [INFO] 
* 2023-07-26 04:26:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-26 04:26:42 (4089) [INFO] 
* 2023-07-26 04:27:24 (4102) [INFO] 
* 2023-07-26 04:27:24 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-26 04:27:24 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-26 04:27:24 (4119) [INFO] 
* 2023-07-26 04:27:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-26 04:27:24 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-26 04:27:26 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-26 04:27:26 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-26 04:27:26 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-26 04:27:26 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-26 04:27: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-07-26 04:27:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-26 04:27:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NVYaNDFKZD/ea_profile.json
* 2023-07-26 04:27:53 (2259) [INFO] Backed up EA4 profile to /tmp/NVYaNDFKZD/ea_profile.json
* 2023-07-26 04:27:54 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-26 04:27:54 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-27 04:26:46 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-27 04:26:46 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-27 04:26:46 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-27 04:26:46 (4089) [INFO] 
* 2023-07-27 04:26:47 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-27 04:26:47 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-27 04:26:47 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-27 04:26:47 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-27 04:26:47 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-27 04:26:47 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-27 04:26:47 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-27 04:26:47 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-27 04:26:47 (4119) [INFO] 
* 2023-07-27 04:26:47 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-27 04:26:47 (4089) [INFO] 
* 2023-07-27 04:27:29 (4102) [INFO] 
* 2023-07-27 04:27:29 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-27 04:27:29 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-27 04:27:29 (4119) [INFO] 
* 2023-07-27 04:27:29 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-27 04:27:29 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-27 04:27:32 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-27 04:27:32 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-27 04:27:32 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-27 04:27:32 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-27 04:27: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-07-27 04:28:04 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-27 04:28:04 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bx1Fb66xIl/ea_profile.json
* 2023-07-27 04:28:05 (2259) [INFO] Backed up EA4 profile to /tmp/bx1Fb66xIl/ea_profile.json
* 2023-07-27 04:28:05 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-27 04:28:05 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-28 04:28:25 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-28 04:28:25 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-28 04:28:25 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-28 04:28:25 (4089) [INFO] 
* 2023-07-28 04:28:26 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-28 04:28:26 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-28 04:28:26 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-28 04:28:26 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-28 04:28:26 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-28 04:28:26 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-28 04:28:26 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-28 04:28:26 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-28 04:28:26 (4119) [INFO] 
* 2023-07-28 04:28:26 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-28 04:28:26 (4089) [INFO] 
* 2023-07-28 04:29:12 (4102) [INFO] 
* 2023-07-28 04:29:12 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-28 04:29:12 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-28 04:29:12 (4119) [INFO] 
* 2023-07-28 04:29:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-28 04:29:12 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-28 04:29:14 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-28 04:29:14 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-28 04:29:14 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-28 04:29:14 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-28 04:29:14 (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 04:29:43 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-28 04:29:43 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4unsM62o0Q/ea_profile.json
* 2023-07-28 04:29:44 (2259) [INFO] Backed up EA4 profile to /tmp/4unsM62o0Q/ea_profile.json
* 2023-07-28 04:29:45 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-28 04:29:45 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-29 04:27:33 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-29 04:27:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-29 04:27:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-29 04:27:33 (4089) [INFO] 
* 2023-07-29 04:27:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-29 04:27:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-29 04:27:34 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-29 04:27:34 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-29 04:27:34 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-29 04:27:34 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-29 04:27:34 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-29 04:27:34 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-29 04:27:34 (4119) [INFO] 
* 2023-07-29 04:27:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-29 04:27:34 (4089) [INFO] 
* 2023-07-29 04:28:15 (4102) [INFO] 
* 2023-07-29 04:28:15 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-29 04:28:15 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-29 04:28:15 (4119) [INFO] 
* 2023-07-29 04:28:15 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-29 04:28:15 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-29 04:28:19 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-29 04:28:19 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-29 04:28:19 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-29 04:28:19 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-29 04:28:19 (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 04:28:46 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-29 04:28:46 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MAAwrXgKw9/ea_profile.json
* 2023-07-29 04:28:47 (2259) [INFO] Backed up EA4 profile to /tmp/MAAwrXgKw9/ea_profile.json
* 2023-07-29 04:28:47 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-29 04:28:47 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-30 04:27:34 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-30 04:27:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-30 04:27:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-30 04:27:34 (4089) [INFO] 
* 2023-07-30 04:27:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-30 04:27:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-30 04:27:35 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-30 04:27:35 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-30 04:27:35 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-30 04:27:35 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-30 04:27:35 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-30 04:27:35 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-30 04:27:35 (4119) [INFO] 
* 2023-07-30 04:27:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-30 04:27:35 (4089) [INFO] 
* 2023-07-30 04:28:16 (4102) [INFO] 
* 2023-07-30 04:28:16 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-30 04:28:16 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-30 04:28:16 (4119) [INFO] 
* 2023-07-30 04:28:16 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-30 04:28:16 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-30 04:28:19 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-30 04:28:19 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-30 04:28:19 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-30 04:28:19 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-30 04:28:19 (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 04:28:45 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-30 04:28:45 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aCbc0DEaYo/ea_profile.json
* 2023-07-30 04:28:46 (2259) [INFO] Backed up EA4 profile to /tmp/aCbc0DEaYo/ea_profile.json
* 2023-07-30 04:28:47 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-30 04:28:47 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-31 04:26:32 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-07-31 04:26:32 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-31 04:26:32 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-31 04:26:32 (4089) [INFO] 
* 2023-07-31 04:26:32 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-31 04:26:32 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-07-31 04:26:32 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-31 04:26:32 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-31 04:26:32 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-31 04:26:32 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-07-31 04:26:32 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-07-31 04:26:32 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-07-31 04:26:32 (4119) [INFO] 
* 2023-07-31 04:26:32 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-31 04:26:32 (4089) [INFO] 
* 2023-07-31 04:27:01 (4102) [INFO] 
* 2023-07-31 04:27:01 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-07-31 04:27:01 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-07-31 04:27:01 (4119) [INFO] 
* 2023-07-31 04:27:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-31 04:27:01 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-31 04:27:03 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-07-31 04:27:03 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-07-31 04:27:03 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-07-31 04:27:03 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-07-31 04:27: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-31 04:27:28 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-31 04:27:28 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F3e1BffRg6/ea_profile.json
* 2023-07-31 04:27:29 (2259) [INFO] Backed up EA4 profile to /tmp/F3e1BffRg6/ea_profile.json
* 2023-07-31 04:27:29 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-07-31 04:27:29 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-01 04:27:22 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-01 04:27:22 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-01 04:27:22 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-01 04:27:22 (4089) [INFO] 
* 2023-08-01 04:27:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-01 04:27:23 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-01 04:27:23 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-01 04:27:23 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-01 04:27:23 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-01 04:27:23 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-01 04:27:23 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-01 04:27:23 (4102) [INFO] Other repos take up 3.9 M of disk space (use --verbose for details)
* 2023-08-01 04:27:23 (4119) [INFO] 
* 2023-08-01 04:27:23 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-01 04:27:23 (4089) [INFO] 
* 2023-08-01 04:28:06 (4102) [INFO] 
* 2023-08-01 04:28:06 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-08-01 04:28:06 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-01 04:28:06 (4119) [INFO] 
* 2023-08-01 04:28:06 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-01 04:28:06 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-01 04:28:08 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-01 04:28:08 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-01 04:28:08 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-01 04:28:08 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-01 04:28:08 (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 04:28:35 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-01 04:28:35 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2SBPUWBWV7/ea_profile.json
* 2023-08-01 04:28:37 (2259) [INFO] Backed up EA4 profile to /tmp/2SBPUWBWV7/ea_profile.json
* 2023-08-01 04:28:37 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-01 04:28:37 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-02 04:26:40 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-02 04:26:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-02 04:26:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-02 04:26:40 (4089) [INFO] 
* 2023-08-02 04:26:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-02 04:26:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-02 04:26:41 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-02 04:26:41 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-02 04:26:41 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-02 04:26:41 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-02 04:26:41 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-02 04:26:41 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-02 04:26:41 (4119) [INFO] 
* 2023-08-02 04:26:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-02 04:26:41 (4089) [INFO] 
* 2023-08-02 04:27:20 (4102) [INFO] 
* 2023-08-02 04:27:20 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-08-02 04:27:20 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-02 04:27:20 (4119) [INFO] 
* 2023-08-02 04:27:20 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-02 04:27:20 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-02 04:27:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-02 04:27:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-02 04:27:23 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-02 04:27:23 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-02 04:27: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-08-02 04:27:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-02 04:27:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gBBDoOYTI5/ea_profile.json
* 2023-08-02 04:27:51 (2259) [INFO] Backed up EA4 profile to /tmp/gBBDoOYTI5/ea_profile.json
* 2023-08-02 04:27:51 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-02 04:27:51 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-03 04:28:04 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-03 04:28:04 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-03 04:28:04 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-03 04:28:04 (4089) [INFO] 
* 2023-08-03 04:28:05 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-03 04:28:05 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-03 04:28:05 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-03 04:28:05 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-03 04:28:05 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-03 04:28:05 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-03 04:28:05 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-03 04:28:05 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-03 04:28:05 (4119) [INFO] 
* 2023-08-03 04:28:05 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-03 04:28:05 (4089) [INFO] 
* 2023-08-03 04:28:43 (4102) [INFO] 
* 2023-08-03 04:28:43 (4102) [INFO] kernel.x86_64                     3.10.0-1160.92.1.el7                   updates
* 2023-08-03 04:28:43 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-03 04:28:43 (4119) [INFO] 
* 2023-08-03 04:28:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-03 04:28:43 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-03 04:28:45 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-03 04:28:45 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-03 04:28:45 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-03 04:28:45 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-03 04:28: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-08-03 04:29:12 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-03 04:29:12 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SQkzLlsr0z/ea_profile.json
* 2023-08-03 04:29:13 (2259) [INFO] Backed up EA4 profile to /tmp/SQkzLlsr0z/ea_profile.json
* 2023-08-03 04:29:13 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-03 04:29:13 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-04 04:27:07 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-04 04:27:07 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-04 04:27:07 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-04 04:27:07 (4089) [INFO] 
* 2023-08-04 04:27:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-04 04:27:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-04 04:27:07 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-04 04:27:07 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-04 04:27:07 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-04 04:27:07 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-04 04:27:07 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-04 04:27:07 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-04 04:27:07 (4119) [INFO] 
* 2023-08-04 04:27:07 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-04 04:27:07 (4089) [INFO] 
* 2023-08-04 04:27:44 (4102) [INFO] 
* 2023-08-04 04:27:44 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-04 04:27:44 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-04 04:27:44 (4119) [INFO] 
* 2023-08-04 04:27:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-04 04:27:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-04 04:27:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-04 04:27:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-04 04:27:46 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-04 04:27:46 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-04 04:27: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-04 04:28:12 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-04 04:28:12 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IdEoyz_sXQ/ea_profile.json
* 2023-08-04 04:28:13 (2259) [INFO] Backed up EA4 profile to /tmp/IdEoyz_sXQ/ea_profile.json
* 2023-08-04 04:28:14 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-04 04:28:14 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-05 04:27:36 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-05 04:27:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-05 04:27:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-05 04:27:36 (4089) [INFO] 
* 2023-08-05 04:27:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-05 04:27:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-05 04:27:37 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-05 04:27:37 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-05 04:27:37 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-05 04:27:37 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-05 04:27:37 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-05 04:27:37 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-05 04:27:37 (4119) [INFO] 
* 2023-08-05 04:27:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-05 04:27:37 (4089) [INFO] 
* 2023-08-05 04:28:17 (4102) [INFO] 
* 2023-08-05 04:28:17 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-05 04:28:17 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-05 04:28:17 (4119) [INFO] 
* 2023-08-05 04:28:17 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-05 04:28:17 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-05 04:28:21 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-05 04:28:21 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-05 04:28:21 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-05 04:28:21 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-05 04:28:21 (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 04:28:46 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-05 04:28:46 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5cN4ZmqkTE/ea_profile.json
* 2023-08-05 04:28:48 (2259) [INFO] Backed up EA4 profile to /tmp/5cN4ZmqkTE/ea_profile.json
* 2023-08-05 04:28:48 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-05 04:28:48 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-06 04:27:32 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-06 04:27:32 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-06 04:27:32 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-06 04:27:32 (4089) [INFO] 
* 2023-08-06 04:27:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-06 04:27:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-06 04:27:33 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-06 04:27:33 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-06 04:27:33 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-06 04:27:33 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-06 04:27:33 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-06 04:27:33 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-06 04:27:33 (4119) [INFO] 
* 2023-08-06 04:27:33 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-06 04:27:33 (4089) [INFO] 
* 2023-08-06 04:28:12 (4102) [INFO] 
* 2023-08-06 04:28:12 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-06 04:28:12 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-06 04:28:12 (4119) [INFO] 
* 2023-08-06 04:28:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-06 04:28:12 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-06 04:28:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-06 04:28:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-06 04:28:15 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-06 04:28:15 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-06 04:28: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-06 04:28:42 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-06 04:28:42 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kapncT2UMO/ea_profile.json
* 2023-08-06 04:28:43 (2259) [INFO] Backed up EA4 profile to /tmp/kapncT2UMO/ea_profile.json
* 2023-08-06 04:28:43 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-06 04:28:43 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-07 04:26:39 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-07 04:26:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-07 04:26:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-07 04:26:39 (4089) [INFO] 
* 2023-08-07 04:26:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-07 04:26:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-07 04:26:39 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-07 04:26:39 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-07 04:26:39 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-07 04:26:39 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-07 04:26:39 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-07 04:26:40 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-07 04:26:40 (4119) [INFO] 
* 2023-08-07 04:26:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-07 04:26:40 (4089) [INFO] 
* 2023-08-07 04:27:22 (4102) [INFO] 
* 2023-08-07 04:27:22 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-07 04:27:22 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-07 04:27:22 (4119) [INFO] 
* 2023-08-07 04:27:22 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-07 04:27:22 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-07 04:27:25 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-07 04:27:25 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-07 04:27:25 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-07 04:27:25 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-07 04:27: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-07 04:27:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-07 04:27:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/siGMHQXawW/ea_profile.json
* 2023-08-07 04:27:52 (2259) [INFO] Backed up EA4 profile to /tmp/siGMHQXawW/ea_profile.json
* 2023-08-07 04:27:53 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-07 04:27:53 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-08 04:26:37 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-08 04:26:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-08 04:26:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-08 04:26:37 (4089) [INFO] 
* 2023-08-08 04:26:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-08 04:26:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-08 04:26:38 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-08 04:26:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-08 04:26:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-08 04:26:38 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-08 04:26:38 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-08 04:26:38 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-08 04:26:38 (4119) [INFO] 
* 2023-08-08 04:26:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-08 04:26:38 (4089) [INFO] 
* 2023-08-08 04:27:18 (4102) [INFO] 
* 2023-08-08 04:27:18 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-08 04:27:18 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-08 04:27:19 (4119) [INFO] 
* 2023-08-08 04:27:19 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-08 04:27:19 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-08 04:27:21 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-08 04:27:21 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-08 04:27:21 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-08 04:27:21 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-08 04:27:21 (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 04:27:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-08 04:27:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sUiUWgPtKb/ea_profile.json
* 2023-08-08 04:27:48 (2259) [INFO] Backed up EA4 profile to /tmp/sUiUWgPtKb/ea_profile.json
* 2023-08-08 04:27:49 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-08 04:27:49 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-09 04:26:50 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-09 04:26:50 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-09 04:26:50 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-09 04:26:50 (4089) [INFO] 
* 2023-08-09 04:26:51 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-09 04:26:51 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-09 04:26:51 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-09 04:26:51 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-09 04:26:51 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-09 04:26:51 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-09 04:26:51 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-09 04:26:51 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-09 04:26:51 (4119) [INFO] 
* 2023-08-09 04:26:51 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-09 04:26:51 (4089) [INFO] 
* 2023-08-09 04:27:18 (4102) [INFO] 
* 2023-08-09 04:27:18 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-09 04:27:18 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-09 04:27:18 (4119) [INFO] 
* 2023-08-09 04:27:18 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-09 04:27:18 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-09 04:27:20 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-09 04:27:20 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-09 04:27:20 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-09 04:27:20 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-09 04:27: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-08-09 04:27:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-09 04:27:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_J_2rzJa7N/ea_profile.json
* 2023-08-09 04:27:45 (2259) [INFO] Backed up EA4 profile to /tmp/_J_2rzJa7N/ea_profile.json
* 2023-08-09 04:27:46 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-09 04:27:46 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-10 04:28:13 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-10 04:28:13 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-10 04:28:13 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-10 04:28:13 (4089) [INFO] 
* 2023-08-10 04:28:13 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-10 04:28:13 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-10 04:28:13 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-10 04:28:13 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-10 04:28:13 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-10 04:28:13 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-10 04:28:13 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-10 04:28:14 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-10 04:28:14 (4119) [INFO] 
* 2023-08-10 04:28:14 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-10 04:28:14 (4089) [INFO] 
* 2023-08-10 04:28:49 (4102) [INFO] 
* 2023-08-10 04:28:49 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-10 04:28:49 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-10 04:28:49 (4119) [INFO] 
* 2023-08-10 04:28:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-10 04:28:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-10 04:28:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-10 04:28:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-10 04:28:51 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-10 04:28:51 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-10 04:28: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-08-10 04:29:19 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-10 04:29:19 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Y2EqDoumPW/ea_profile.json
* 2023-08-10 04:29:20 (2259) [INFO] Backed up EA4 profile to /tmp/Y2EqDoumPW/ea_profile.json
* 2023-08-10 04:29:20 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-10 04:29:20 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-11 04:26:31 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-11 04:26:31 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-11 04:26:31 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-11 04:26:31 (4089) [INFO] 
* 2023-08-11 04:26:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-11 04:26:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-11 04:26:31 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-11 04:26:31 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-11 04:26:31 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-11 04:26:31 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-11 04:26:31 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-11 04:26:32 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-11 04:26:32 (4119) [INFO] 
* 2023-08-11 04:26:32 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-11 04:26:32 (4089) [INFO] 
* 2023-08-11 04:27:13 (4102) [INFO] 
* 2023-08-11 04:27:13 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-11 04:27:13 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-11 04:27:13 (4119) [INFO] 
* 2023-08-11 04:27:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-11 04:27:13 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-11 04:27:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-11 04:27:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-11 04:27:16 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-11 04:27:16 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-11 04:27:16 (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 04:27:41 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-11 04:27:41 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/U6bYcrb9td/ea_profile.json
* 2023-08-11 04:27:42 (2259) [INFO] Backed up EA4 profile to /tmp/U6bYcrb9td/ea_profile.json
* 2023-08-11 04:27:43 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-11 04:27:43 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-12 04:27:30 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-12 04:27:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-12 04:27:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-12 04:27:30 (4089) [INFO] 
* 2023-08-12 04:27:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-12 04:27:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-12 04:27:31 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-12 04:27:31 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-12 04:27:31 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-12 04:27:31 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-12 04:27:31 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-12 04:27:31 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-12 04:27:31 (4119) [INFO] 
* 2023-08-12 04:27:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-12 04:27:31 (4089) [INFO] 
* 2023-08-12 04:27:58 (4102) [INFO] 
* 2023-08-12 04:27:58 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-12 04:27:58 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-12 04:27:58 (4119) [INFO] 
* 2023-08-12 04:27:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-12 04:27:58 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-12 04:28:00 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-12 04:28:00 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-12 04:28:00 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-12 04:28:00 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-12 04:28: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-08-12 04:28:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-12 04:28:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Wcno79cGVb/ea_profile.json
* 2023-08-12 04:28:25 (2259) [INFO] Backed up EA4 profile to /tmp/Wcno79cGVb/ea_profile.json
* 2023-08-12 04:28:26 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-12 04:28:26 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-13 04:27:30 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-13 04:27:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-13 04:27:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-13 04:27:30 (4089) [INFO] 
* 2023-08-13 04:27:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-13 04:27:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-13 04:27:31 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-13 04:27:31 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-13 04:27:31 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-13 04:27:31 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-13 04:27:31 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-13 04:27:31 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-13 04:27:31 (4119) [INFO] 
* 2023-08-13 04:27:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-13 04:27:31 (4089) [INFO] 
* 2023-08-13 04:28:13 (4102) [INFO] 
* 2023-08-13 04:28:13 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-13 04:28:13 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-13 04:28:13 (4119) [INFO] 
* 2023-08-13 04:28:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-13 04:28:13 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-13 04:28:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-13 04:28:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-13 04:28:15 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-13 04:28:15 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-13 04:28: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-13 04:28:41 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-13 04:28:41 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZKWQWjuLwz/ea_profile.json
* 2023-08-13 04:28:42 (2259) [INFO] Backed up EA4 profile to /tmp/ZKWQWjuLwz/ea_profile.json
* 2023-08-13 04:28:43 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-13 04:28:43 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-14 04:26:32 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-14 04:26:32 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-14 04:26:32 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-14 04:26:32 (4089) [INFO] 
* 2023-08-14 04:26:32 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-14 04:26:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-14 04:26:33 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-14 04:26:33 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-14 04:26:33 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-14 04:26:33 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-14 04:26:33 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-14 04:26:33 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-14 04:26:33 (4119) [INFO] 
* 2023-08-14 04:26:33 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-14 04:26:33 (4089) [INFO] 
* 2023-08-14 04:27:12 (4102) [INFO] 
* 2023-08-14 04:27:12 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-14 04:27:12 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-14 04:27:12 (4119) [INFO] 
* 2023-08-14 04:27:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-14 04:27:12 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-14 04:27:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-14 04:27:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-14 04:27:15 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-14 04:27:15 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-14 04:27: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-14 04:27:41 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-14 04:27:41 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GWpcTqbGLL/ea_profile.json
* 2023-08-14 04:27:42 (2259) [INFO] Backed up EA4 profile to /tmp/GWpcTqbGLL/ea_profile.json
* 2023-08-14 04:27:42 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-14 04:27:42 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-15 04:28:21 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-15 04:28:21 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-15 04:28:21 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-15 04:28:21 (4089) [INFO] 
* 2023-08-15 04:28:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-15 04:28:22 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-15 04:28:22 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-15 04:28:22 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-15 04:28:22 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-15 04:28:22 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-15 04:28:22 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-15 04:28:22 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-15 04:28:22 (4119) [INFO] 
* 2023-08-15 04:28:22 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-15 04:28:22 (4089) [INFO] 
* 2023-08-15 04:29:14 (4102) [INFO] 
* 2023-08-15 04:29:14 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-15 04:29:14 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-15 04:29:14 (4119) [INFO] 
* 2023-08-15 04:29:14 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-15 04:29:14 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-15 04:29:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-15 04:29:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-15 04:29:16 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-15 04:29:16 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-15 04:29:16 (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 04:30:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-15 04:30:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OligDFlmc_/ea_profile.json
* 2023-08-15 04:30:06 (2259) [INFO] Backed up EA4 profile to /tmp/OligDFlmc_/ea_profile.json
* 2023-08-15 04:30:07 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-15 04:30:07 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-16 04:26:53 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-16 04:26:53 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-16 04:26:53 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-16 04:26:53 (4089) [INFO] 
* 2023-08-16 04:26:53 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-16 04:26:54 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-16 04:26:54 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-16 04:26:54 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-16 04:26:54 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-16 04:26:54 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-16 04:26:54 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-16 04:26:54 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-16 04:26:54 (4119) [INFO] 
* 2023-08-16 04:26:54 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-16 04:26:54 (4089) [INFO] 
* 2023-08-16 04:27:34 (4102) [INFO] 
* 2023-08-16 04:27:34 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-16 04:27:34 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-16 04:27:34 (4119) [INFO] 
* 2023-08-16 04:27:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-16 04:27:34 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-16 04:27:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-16 04:27:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-16 04:27:37 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-16 04:27:37 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-16 04:27: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-16 04:28:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-16 04:28:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LW_HtASJNG/ea_profile.json
* 2023-08-16 04:28:06 (2259) [INFO] Backed up EA4 profile to /tmp/LW_HtASJNG/ea_profile.json
* 2023-08-16 04:28:07 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-16 04:28:07 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-17 04:27:54 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-17 04:27:54 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-17 04:27:54 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-17 04:27:54 (4089) [INFO] 
* 2023-08-17 04:27:54 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-17 04:27:54 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-17 04:27:54 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-17 04:27:54 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-17 04:27:54 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-17 04:27:54 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-17 04:27:54 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-17 04:27:55 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-17 04:27:55 (4119) [INFO] 
* 2023-08-17 04:27:55 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-17 04:27:55 (4089) [INFO] 
* 2023-08-17 04:28:30 (4102) [INFO] 
* 2023-08-17 04:28:30 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-17 04:28:30 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-17 04:28:30 (4119) [INFO] 
* 2023-08-17 04:28:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-17 04:28:30 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-17 04:28:32 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-17 04:28:32 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-17 04:28:32 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-17 04:28:32 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-17 04:28:32 (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 04:29:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-17 04:29:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HvxzBBcfD5/ea_profile.json
* 2023-08-17 04:29:02 (2259) [INFO] Backed up EA4 profile to /tmp/HvxzBBcfD5/ea_profile.json
* 2023-08-17 04:29:02 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-17 04:29:02 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-18 04:26:42 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-18 04:26:42 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-18 04:26:42 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-18 04:26:42 (4089) [INFO] 
* 2023-08-18 04:26:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-18 04:26:43 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-18 04:26:43 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-18 04:26:43 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-18 04:26:43 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-18 04:26:43 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-18 04:26:43 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-18 04:26:43 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-18 04:26:43 (4119) [INFO] 
* 2023-08-18 04:26:43 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-18 04:26:43 (4089) [INFO] 
* 2023-08-18 04:27:24 (4102) [INFO] 
* 2023-08-18 04:27:24 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-18 04:27:24 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-18 04:27:24 (4119) [INFO] 
* 2023-08-18 04:27:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-18 04:27:24 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-18 04:27:27 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-18 04:27:27 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-18 04:27:27 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-18 04:27:27 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-18 04:27:27 (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 04:27:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-18 04:27:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pyHcNFzwqt/ea_profile.json
* 2023-08-18 04:27:57 (2259) [INFO] Backed up EA4 profile to /tmp/pyHcNFzwqt/ea_profile.json
* 2023-08-18 04:27:57 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-18 04:27:57 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-19 04:27:54 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-19 04:27:54 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-19 04:27:54 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-19 04:27:54 (4089) [INFO] 
* 2023-08-19 04:27:55 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-19 04:27:55 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-19 04:27:55 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-19 04:27:55 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-19 04:27:55 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-19 04:27:55 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-19 04:27:55 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-19 04:27:56 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-19 04:27:56 (4119) [INFO] 
* 2023-08-19 04:27:56 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-19 04:27:56 (4089) [INFO] 
* 2023-08-19 04:28:35 (4102) [INFO] 
* 2023-08-19 04:28:35 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-19 04:28:35 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-19 04:28:36 (4119) [INFO] 
* 2023-08-19 04:28:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-19 04:28:36 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-19 04:28:38 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-19 04:28:38 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-19 04:28:38 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-19 04:28:38 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-19 04:28: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-08-19 04:29:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-19 04:29:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Gdo2NJDFIj/ea_profile.json
* 2023-08-19 04:29:11 (2259) [INFO] Backed up EA4 profile to /tmp/Gdo2NJDFIj/ea_profile.json
* 2023-08-19 04:29:11 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-19 04:29:12 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-20 04:27:44 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-20 04:27:44 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-20 04:27:44 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-20 04:27:44 (4089) [INFO] 
* 2023-08-20 04:27:44 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-20 04:27:45 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-20 04:27:45 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-20 04:27:45 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-20 04:27:45 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-20 04:27:45 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-20 04:27:45 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-20 04:27:45 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-20 04:27:45 (4119) [INFO] 
* 2023-08-20 04:27:45 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-20 04:27:45 (4089) [INFO] 
* 2023-08-20 04:28:27 (4102) [INFO] 
* 2023-08-20 04:28:27 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-20 04:28:27 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-20 04:28:27 (4119) [INFO] 
* 2023-08-20 04:28:27 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-20 04:28:27 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-20 04:28:31 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-20 04:28:31 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-20 04:28:31 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-20 04:28:31 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-20 04:28: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-08-20 04:28:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-20 04:28:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VBcU4Pbjan/ea_profile.json
* 2023-08-20 04:28:59 (2259) [INFO] Backed up EA4 profile to /tmp/VBcU4Pbjan/ea_profile.json
* 2023-08-20 04:29:00 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-20 04:29:00 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-21 04:26:45 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-21 04:26:45 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-21 04:26:45 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-21 04:26:45 (4089) [INFO] 
* 2023-08-21 04:26:45 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-21 04:26:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-21 04:26:46 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-21 04:26:46 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-21 04:26:46 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-21 04:26:46 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-21 04:26:46 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-21 04:26:46 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-21 04:26:46 (4119) [INFO] 
* 2023-08-21 04:26:46 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-21 04:26:46 (4089) [INFO] 
* 2023-08-21 04:27:26 (4102) [INFO] 
* 2023-08-21 04:27:26 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-21 04:27:26 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-21 04:27:26 (4119) [INFO] 
* 2023-08-21 04:27:26 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-21 04:27:26 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-21 04:27:30 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-21 04:27:30 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-21 04:27:30 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-21 04:27:30 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-21 04:27: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-08-21 04:27:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-21 04:27:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/51rlYJxtfr/ea_profile.json
* 2023-08-21 04:27:59 (2259) [INFO] Backed up EA4 profile to /tmp/51rlYJxtfr/ea_profile.json
* 2023-08-21 04:27:59 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-21 04:27:59 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-22 04:28:25 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-22 04:28:25 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-22 04:28:25 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-22 04:28:25 (4089) [INFO] 
* 2023-08-22 04:28:26 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-22 04:28:26 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-22 04:28:26 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-22 04:28:26 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-22 04:28:26 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-22 04:28:26 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-22 04:28:26 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-22 04:28:27 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-22 04:28:27 (4119) [INFO] 
* 2023-08-22 04:28:27 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-22 04:28:27 (4089) [INFO] 
* 2023-08-22 04:29:16 (4102) [INFO] 
* 2023-08-22 04:29:16 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-22 04:29:16 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-22 04:29:16 (4119) [INFO] 
* 2023-08-22 04:29:16 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-22 04:29:16 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-22 04:29:19 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-22 04:29:19 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-22 04:29:19 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-22 04:29:19 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-22 04:29:19 (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 04:29:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-22 04:29:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mJIYDrmqek/ea_profile.json
* 2023-08-22 04:29:48 (2259) [INFO] Backed up EA4 profile to /tmp/mJIYDrmqek/ea_profile.json
* 2023-08-22 04:29:49 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-22 04:29:49 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-23 04:26:42 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-23 04:26:42 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-23 04:26:42 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-23 04:26:42 (4089) [INFO] 
* 2023-08-23 04:26:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-23 04:26:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-23 04:26:42 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-23 04:26:42 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-23 04:26:42 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-23 04:26:42 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-23 04:26:42 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-23 04:26:42 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-23 04:26:42 (4119) [INFO] 
* 2023-08-23 04:26:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-23 04:26:42 (4089) [INFO] 
* 2023-08-23 04:27:25 (4102) [INFO] 
* 2023-08-23 04:27:25 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-23 04:27:25 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-23 04:27:25 (4119) [INFO] 
* 2023-08-23 04:27:25 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-23 04:27:25 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-23 04:27:29 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-23 04:27:29 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-23 04:27:29 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-23 04:27:29 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-23 04:27:29 (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 04:27:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-23 04:27:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AZ6MOCfSkn/ea_profile.json
* 2023-08-23 04:27:57 (2259) [INFO] Backed up EA4 profile to /tmp/AZ6MOCfSkn/ea_profile.json
* 2023-08-23 04:27:58 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-23 04:27:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-24 04:27:08 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-24 04:27:08 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-24 04:27:08 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-24 04:27:08 (4089) [INFO] 
* 2023-08-24 04:27:09 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-24 04:27:09 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-24 04:27:09 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-24 04:27:09 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-24 04:27:09 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-24 04:27:09 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-24 04:27:09 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-24 04:27:09 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-24 04:27:09 (4119) [INFO] 
* 2023-08-24 04:27:09 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-24 04:27:09 (4089) [INFO] 
* 2023-08-24 04:27:47 (4102) [INFO] 
* 2023-08-24 04:27:47 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-24 04:27:47 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-24 04:27:48 (4119) [INFO] 
* 2023-08-24 04:27:48 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-24 04:27:48 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-24 04:27:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-24 04:27:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-24 04:27:50 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-24 04:27:50 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-24 04:27: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-24 04:28:23 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-24 04:28:23 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/su0LiMkZpa/ea_profile.json
* 2023-08-24 04:28:24 (2259) [INFO] Backed up EA4 profile to /tmp/su0LiMkZpa/ea_profile.json
* 2023-08-24 04:28:25 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-24 04:28:25 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-25 04:26:42 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-25 04:26:42 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-25 04:26:42 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-25 04:26:42 (4089) [INFO] 
* 2023-08-25 04:26:43 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-25 04:26:43 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-25 04:26:43 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-25 04:26:43 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-25 04:26:43 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-25 04:26:43 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-25 04:26:43 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-25 04:26:44 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-25 04:26:44 (4119) [INFO] 
* 2023-08-25 04:26:44 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-25 04:26:44 (4089) [INFO] 
* 2023-08-25 04:27:25 (4102) [INFO] 
* 2023-08-25 04:27:25 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-25 04:27:25 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-25 04:27:25 (4119) [INFO] 
* 2023-08-25 04:27:25 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-25 04:27:25 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-25 04:27:28 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-25 04:27:28 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-25 04:27:28 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-25 04:27:28 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-25 04:27:28 (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 04:27:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-25 04:27:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bDYsfeAMXk/ea_profile.json
* 2023-08-25 04:27:58 (2259) [INFO] Backed up EA4 profile to /tmp/bDYsfeAMXk/ea_profile.json
* 2023-08-25 04:27:59 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-25 04:28:00 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-26 04:28:44 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-26 04:28:44 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-26 04:28:44 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-26 04:28:44 (4089) [INFO] 
* 2023-08-26 04:28:45 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-26 04:28:45 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-26 04:28:45 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-26 04:28:45 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-26 04:28:45 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-26 04:28:45 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-26 04:28:45 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-26 04:28:45 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-26 04:28:45 (4119) [INFO] 
* 2023-08-26 04:28:45 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-26 04:28:45 (4089) [INFO] 
* 2023-08-26 04:29:14 (4102) [INFO] 
* 2023-08-26 04:29:14 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-26 04:29:14 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-26 04:29:14 (4119) [INFO] 
* 2023-08-26 04:29:14 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-26 04:29:14 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-26 04:29:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-26 04:29:16 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-26 04:29:16 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-26 04:29:16 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-26 04:29:16 (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 04:29:43 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-26 04:29:43 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oVJZuBIN5a/ea_profile.json
* 2023-08-26 04:29:44 (2259) [INFO] Backed up EA4 profile to /tmp/oVJZuBIN5a/ea_profile.json
* 2023-08-26 04:29:44 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-26 04:29:44 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-27 04:27:39 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-27 04:27:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-27 04:27:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-27 04:27:39 (4089) [INFO] 
* 2023-08-27 04:27:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-27 04:27:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-27 04:27:40 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-27 04:27:40 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-27 04:27:40 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-27 04:27:40 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-27 04:27:40 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-27 04:27:40 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-27 04:27:40 (4119) [INFO] 
* 2023-08-27 04:27:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-27 04:27:40 (4089) [INFO] 
* 2023-08-27 04:28:24 (4102) [INFO] 
* 2023-08-27 04:28:24 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-27 04:28:24 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-27 04:28:24 (4119) [INFO] 
* 2023-08-27 04:28:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-27 04:28:24 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-27 04:28:27 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-27 04:28:27 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-27 04:28:27 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-27 04:28:27 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-27 04:28:27 (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 04:28:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-27 04:28:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9TseMX9E4I/ea_profile.json
* 2023-08-27 04:29:00 (2259) [INFO] Backed up EA4 profile to /tmp/9TseMX9E4I/ea_profile.json
* 2023-08-27 04:29:01 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-27 04:29:01 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-28 04:26:44 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-28 04:26:44 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-28 04:26:44 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-28 04:26:44 (4089) [INFO] 
* 2023-08-28 04:26:45 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-28 04:26:45 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-28 04:26:45 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-28 04:26:45 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-28 04:26:45 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-28 04:26:45 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-28 04:26:45 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-28 04:26:45 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-28 04:26:45 (4119) [INFO] 
* 2023-08-28 04:26:45 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-28 04:26:45 (4089) [INFO] 
* 2023-08-28 04:27:30 (4102) [INFO] 
* 2023-08-28 04:27:30 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-28 04:27:30 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-28 04:27:30 (4119) [INFO] 
* 2023-08-28 04:27:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-28 04:27:30 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-28 04:27:34 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-28 04:27:34 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-28 04:27:34 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-28 04:27:34 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-28 04:27: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-08-28 04:28:04 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-28 04:28:04 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5v3bQ_nrbT/ea_profile.json
* 2023-08-28 04:28:05 (2259) [INFO] Backed up EA4 profile to /tmp/5v3bQ_nrbT/ea_profile.json
* 2023-08-28 04:28:06 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-28 04:28:06 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-29 04:26:52 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-29 04:26:52 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-29 04:26:52 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-29 04:26:52 (4089) [INFO] 
* 2023-08-29 04:26:52 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-29 04:26:52 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-29 04:26:52 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-29 04:26:52 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-29 04:26:52 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-29 04:26:52 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-29 04:26:52 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-29 04:26:53 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-29 04:26:53 (4119) [INFO] 
* 2023-08-29 04:26:53 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-29 04:26:53 (4089) [INFO] 
* 2023-08-29 04:27:36 (4102) [INFO] 
* 2023-08-29 04:27:36 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-29 04:27:36 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-29 04:27:37 (4119) [INFO] 
* 2023-08-29 04:27:37 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-29 04:27:37 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-29 04:27:40 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-29 04:27:40 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-29 04:27:40 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-29 04:27:40 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-29 04:27:41 (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 04:28:13 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-29 04:28:13 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QBdk8GSFbH/ea_profile.json
* 2023-08-29 04:28:14 (2259) [INFO] Backed up EA4 profile to /tmp/QBdk8GSFbH/ea_profile.json
* 2023-08-29 04:28:14 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-29 04:28:15 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-30 04:26:29 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-30 04:26:29 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-30 04:26:29 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-30 04:26:29 (4089) [INFO] 
* 2023-08-30 04:26:29 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-30 04:26:29 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-30 04:26:29 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-30 04:26:29 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-30 04:26:29 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-30 04:26:29 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-30 04:26:29 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-30 04:26:30 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-30 04:26:30 (4119) [INFO] 
* 2023-08-30 04:26:30 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-30 04:26:30 (4089) [INFO] 
* 2023-08-30 04:26:57 (4102) [INFO] 
* 2023-08-30 04:26:57 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-30 04:26:57 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-30 04:26:57 (4119) [INFO] 
* 2023-08-30 04:26:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-30 04:26:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-30 04:26:59 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-30 04:26:59 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-30 04:26:59 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-30 04:26:59 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-30 04:26: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-30 04:27:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-30 04:27:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RWv6q4OECB/ea_profile.json
* 2023-08-30 04:27:25 (2259) [INFO] Backed up EA4 profile to /tmp/RWv6q4OECB/ea_profile.json
* 2023-08-30 04:27:26 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-30 04:27:26 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-31 04:27:13 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-08-31 04:27:13 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-31 04:27:13 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-31 04:27:13 (4089) [INFO] 
* 2023-08-31 04:27:13 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-31 04:27:13 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-08-31 04:27:13 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-31 04:27:13 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-31 04:27:13 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-31 04:27:13 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-08-31 04:27:13 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-08-31 04:27:14 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-08-31 04:27:14 (4119) [INFO] 
* 2023-08-31 04:27:14 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-31 04:27:14 (4089) [INFO] 
* 2023-08-31 04:27:49 (4102) [INFO] 
* 2023-08-31 04:27:49 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-08-31 04:27:49 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-08-31 04:27:49 (4119) [INFO] 
* 2023-08-31 04:27:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-31 04:27:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-31 04:27:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-08-31 04:27:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-08-31 04:27:51 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-08-31 04:27:51 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-08-31 04:27: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-08-31 04:28:20 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-31 04:28:20 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VVhZop8g06/ea_profile.json
* 2023-08-31 04:28:21 (2259) [INFO] Backed up EA4 profile to /tmp/VVhZop8g06/ea_profile.json
* 2023-08-31 04:28:22 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-08-31 04:28:22 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-01 04:26:50 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-01 04:26:50 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-01 04:26:50 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-01 04:26:50 (4089) [INFO] 
* 2023-09-01 04:26:50 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-01 04:26:50 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-01 04:26:50 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-01 04:26:50 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-01 04:26:50 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-01 04:26:50 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-01 04:26:50 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-01 04:26:50 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-01 04:26:50 (4119) [INFO] 
* 2023-09-01 04:26:50 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-01 04:26:50 (4089) [INFO] 
* 2023-09-01 04:27:17 (4102) [INFO] 
* 2023-09-01 04:27:17 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-01 04:27:17 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-01 04:27:17 (4119) [INFO] 
* 2023-09-01 04:27:17 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-01 04:27:17 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-01 04:27:18 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-01 04:27:18 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-01 04:27:18 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-01 04:27:18 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-01 04:27: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-09-01 04:27:43 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-01 04:27:43 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DiKUf1RoSf/ea_profile.json
* 2023-09-01 04:27:44 (2259) [INFO] Backed up EA4 profile to /tmp/DiKUf1RoSf/ea_profile.json
* 2023-09-01 04:27:44 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-01 04:27:44 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-02 04:27:37 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-02 04:27:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-02 04:27:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-02 04:27:37 (4089) [INFO] 
* 2023-09-02 04:27:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-02 04:27:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-02 04:27:38 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-02 04:27:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-02 04:27:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-02 04:27:38 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-02 04:27:38 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-02 04:27:38 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-02 04:27:38 (4119) [INFO] 
* 2023-09-02 04:27:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-02 04:27:38 (4089) [INFO] 
* 2023-09-02 04:28:22 (4102) [INFO] 
* 2023-09-02 04:28:22 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-02 04:28:22 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-02 04:28:22 (4119) [INFO] 
* 2023-09-02 04:28:22 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-02 04:28:22 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-02 04:28:25 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-02 04:28:25 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-02 04:28:25 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-02 04:28:25 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-02 04:28: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-09-02 04:28:53 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-02 04:28:53 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/h6QuNgg23C/ea_profile.json
* 2023-09-02 04:28:54 (2259) [INFO] Backed up EA4 profile to /tmp/h6QuNgg23C/ea_profile.json
* 2023-09-02 04:28:55 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-02 04:28:55 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-03 04:27:29 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-03 04:27:29 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-03 04:27:29 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-03 04:27:29 (4089) [INFO] 
* 2023-09-03 04:27:29 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-03 04:27:30 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-03 04:27:30 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-03 04:27:30 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-03 04:27:30 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-03 04:27:30 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-03 04:27:30 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-03 04:27:30 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-03 04:27:30 (4119) [INFO] 
* 2023-09-03 04:27:30 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-03 04:27:30 (4089) [INFO] 
* 2023-09-03 04:27:57 (4102) [INFO] 
* 2023-09-03 04:27:57 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-03 04:27:57 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-03 04:27:58 (4119) [INFO] 
* 2023-09-03 04:27:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-03 04:27:58 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-03 04:28:00 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-03 04:28:00 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-03 04:28:00 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-03 04:28:00 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-03 04:28: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-09-03 04:28:25 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-03 04:28:25 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OSJDqRat0D/ea_profile.json
* 2023-09-03 04:28:27 (2259) [INFO] Backed up EA4 profile to /tmp/OSJDqRat0D/ea_profile.json
* 2023-09-03 04:28:27 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-03 04:28:28 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-04 04:26:35 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-04 04:26:35 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-04 04:26:35 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-04 04:26:35 (4089) [INFO] 
* 2023-09-04 04:26:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-04 04:26:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-04 04:26:35 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-04 04:26:35 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-04 04:26:35 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-04 04:26:35 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-04 04:26:35 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-04 04:26:36 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-04 04:26:36 (4119) [INFO] 
* 2023-09-04 04:26:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-04 04:26:36 (4089) [INFO] 
* 2023-09-04 04:27:04 (4102) [INFO] 
* 2023-09-04 04:27:04 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-04 04:27:04 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-04 04:27:04 (4119) [INFO] 
* 2023-09-04 04:27:04 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-04 04:27:04 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-04 04:27:06 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-04 04:27:06 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-04 04:27:06 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-04 04:27:06 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-04 04:27:06 (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 04:27:33 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-04 04:27:33 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4ugOKLNgim/ea_profile.json
* 2023-09-04 04:27:34 (2259) [INFO] Backed up EA4 profile to /tmp/4ugOKLNgim/ea_profile.json
* 2023-09-04 04:27:35 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-04 04:27:35 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-05 04:26:34 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-05 04:26:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-05 04:26:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-05 04:26:34 (4089) [INFO] 
* 2023-09-05 04:26:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-05 04:26:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-05 04:26:34 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-05 04:26:34 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-05 04:26:34 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-05 04:26:34 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-05 04:26:34 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-05 04:26:34 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-05 04:26:34 (4119) [INFO] 
* 2023-09-05 04:26:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-05 04:26:34 (4089) [INFO] 
* 2023-09-05 04:27:04 (4102) [INFO] 
* 2023-09-05 04:27:04 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-05 04:27:04 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-05 04:27:05 (4119) [INFO] 
* 2023-09-05 04:27:05 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-05 04:27:05 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-05 04:27:07 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-05 04:27:07 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-05 04:27:07 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-05 04:27:07 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-05 04:27:07 (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 04:27:33 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-05 04:27:33 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YdEdJUOV2d/ea_profile.json
* 2023-09-05 04:27:34 (2259) [INFO] Backed up EA4 profile to /tmp/YdEdJUOV2d/ea_profile.json
* 2023-09-05 04:27:35 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-05 04:27:35 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-06 04:26:36 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-06 04:26:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-06 04:26:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-06 04:26:36 (4089) [INFO] 
* 2023-09-06 04:26:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-06 04:26:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-06 04:26:37 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-06 04:26:37 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-06 04:26:37 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-06 04:26:37 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-06 04:26:37 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-06 04:26:37 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-06 04:26:37 (4119) [INFO] 
* 2023-09-06 04:26:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-06 04:26:37 (4089) [INFO] 
* 2023-09-06 04:27:06 (4102) [INFO] 
* 2023-09-06 04:27:06 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-06 04:27:06 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-06 04:27:06 (4119) [INFO] 
* 2023-09-06 04:27:06 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-06 04:27:06 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-06 04:27:08 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-06 04:27:08 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-06 04:27:08 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-06 04:27:08 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-06 04:27:08 (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 04:27:34 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-06 04:27:34 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KCRaY5KZLG/ea_profile.json
* 2023-09-06 04:27:35 (2259) [INFO] Backed up EA4 profile to /tmp/KCRaY5KZLG/ea_profile.json
* 2023-09-06 04:27:35 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-06 04:27:35 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-07 04:26:52 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-07 04:26:52 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-07 04:26:52 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-07 04:26:52 (4089) [INFO] 
* 2023-09-07 04:26:53 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-07 04:26:53 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-07 04:26:53 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-07 04:26:53 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-07 04:26:53 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-07 04:26:53 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-07 04:26:53 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-07 04:26:53 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-07 04:26:53 (4119) [INFO] 
* 2023-09-07 04:26:53 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-07 04:26:53 (4089) [INFO] 
* 2023-09-07 04:27:21 (4102) [INFO] 
* 2023-09-07 04:27:21 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-07 04:27:21 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-07 04:27:21 (4119) [INFO] 
* 2023-09-07 04:27:21 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-07 04:27:21 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-07 04:27:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-07 04:27:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-07 04:27:23 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-07 04:27:23 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-07 04:27: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-09-07 04:27:48 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-07 04:27:48 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yN5Fdyg5U9/ea_profile.json
* 2023-09-07 04:27:49 (2259) [INFO] Backed up EA4 profile to /tmp/yN5Fdyg5U9/ea_profile.json
* 2023-09-07 04:27:49 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-07 04:27:49 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-08 04:26:38 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-08 04:26:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-08 04:26:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-08 04:26:38 (4089) [INFO] 
* 2023-09-08 04:26:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-08 04:26:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-08 04:26:39 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-08 04:26:39 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-08 04:26:39 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-08 04:26:39 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-08 04:26:39 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-08 04:26:39 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-08 04:26:39 (4119) [INFO] 
* 2023-09-08 04:26:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-08 04:26:39 (4089) [INFO] 
* 2023-09-08 04:27:07 (4102) [INFO] 
* 2023-09-08 04:27:07 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-08 04:27:07 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-08 04:27:07 (4119) [INFO] 
* 2023-09-08 04:27:07 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-08 04:27:07 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-08 04:27:10 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-08 04:27:10 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-08 04:27:10 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-08 04:27:10 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-08 04:27: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-09-08 04:27:36 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-08 04:27:36 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KuddR2xF81/ea_profile.json
* 2023-09-08 04:27:37 (2259) [INFO] Backed up EA4 profile to /tmp/KuddR2xF81/ea_profile.json
* 2023-09-08 04:27:37 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-08 04:27:37 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-09 04:27:37 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-09 04:27:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-09 04:27:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-09 04:27:37 (4089) [INFO] 
* 2023-09-09 04:27:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-09 04:27:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-09 04:27:38 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-09 04:27:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-09 04:27:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-09 04:27:38 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-09 04:27:38 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-09 04:27:38 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-09 04:27:38 (4119) [INFO] 
* 2023-09-09 04:27:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-09 04:27:38 (4089) [INFO] 
* 2023-09-09 04:28:09 (4102) [INFO] 
* 2023-09-09 04:28:09 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-09 04:28:09 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-09 04:28:09 (4119) [INFO] 
* 2023-09-09 04:28:09 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-09 04:28:09 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-09 04:28:12 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-09 04:28:12 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-09 04:28:12 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-09 04:28:12 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-09 04:28: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-09-09 04:28:38 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-09 04:28:38 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6f_6Dn0hdS/ea_profile.json
* 2023-09-09 04:28:39 (2259) [INFO] Backed up EA4 profile to /tmp/6f_6Dn0hdS/ea_profile.json
* 2023-09-09 04:28:40 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-09 04:28:40 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-10 04:27:33 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-10 04:27:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-10 04:27:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-10 04:27:33 (4089) [INFO] 
* 2023-09-10 04:27:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-10 04:27:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-10 04:27:33 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-10 04:27:33 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-10 04:27:33 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-10 04:27:33 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-10 04:27:33 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-10 04:27:34 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-10 04:27:34 (4119) [INFO] 
* 2023-09-10 04:27:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-10 04:27:34 (4089) [INFO] 
* 2023-09-10 04:28:02 (4102) [INFO] 
* 2023-09-10 04:28:02 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-10 04:28:02 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-10 04:28:02 (4119) [INFO] 
* 2023-09-10 04:28:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-10 04:28:02 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-10 04:28:05 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-10 04:28:05 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-10 04:28:05 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-10 04:28:05 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-10 04:28: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-09-10 04:28:31 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-10 04:28:31 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/isLAjZoUhA/ea_profile.json
* 2023-09-10 04:28:33 (2259) [INFO] Backed up EA4 profile to /tmp/isLAjZoUhA/ea_profile.json
* 2023-09-10 04:28:34 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-10 04:28:34 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-11 04:26:40 (460) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-11 04:26:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-11 04:26:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-11 04:26:40 (4089) [INFO] 
* 2023-09-11 04:26:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-11 04:26:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-11 04:26:40 (4102) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-11 04:26:40 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-11 04:26:40 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-11 04:26:40 (4102) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-11 04:26:40 (4102) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-11 04:26:40 (4102) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-11 04:26:40 (4119) [INFO] 
* 2023-09-11 04:26:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-11 04:26:40 (4089) [INFO] 
* 2023-09-11 04:27:12 (4102) [INFO] 
* 2023-09-11 04:27:12 (4102) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-11 04:27:12 (4102) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-11 04:27:12 (4119) [INFO] 
* 2023-09-11 04:27:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-11 04:27:12 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-11 04:27:14 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-11 04:27:14 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-11 04:27:14 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-11 04:27:14 (1636) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-11 04:27:14 (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 04:27:41 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-11 04:27:41 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SG6HOKwXlg/ea_profile.json
* 2023-09-11 04:27:42 (2259) [INFO] Backed up EA4 profile to /tmp/SG6HOKwXlg/ea_profile.json
* 2023-09-11 04:27:42 (153) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-11 04:27:42 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-12 04:26:38 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-12 04:26:38 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-12 04:26:38 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-12 04:26:38 (4229) [INFO] 
* 2023-09-12 04:26:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-12 04:26:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-12 04:26:39 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-12 04:26:39 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-12 04:26:39 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-12 04:26:39 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-12 04:26:39 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-12 04:26:39 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-12 04:26:39 (4259) [INFO] 
* 2023-09-12 04:26:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-12 04:26:39 (4229) [INFO] 
* 2023-09-12 04:27:08 (4242) [INFO] 
* 2023-09-12 04:27:08 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-12 04:27:08 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-12 04:27:09 (4259) [INFO] 
* 2023-09-12 04:27:09 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-12 04:27:09 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-12 04:27:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-12 04:27:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-12 04:27:11 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-12 04:27:11 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-12 04:27: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-12 04:27:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-12 04:27:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r802y99Y3_/ea_profile.json
* 2023-09-12 04:27:38 (2293) [INFO] Backed up EA4 profile to /tmp/r802y99Y3_/ea_profile.json
* 2023-09-12 04:27:39 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-12 04:27:39 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-13 04:26:32 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-13 04:26:32 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-13 04:26:32 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-13 04:26:32 (4229) [INFO] 
* 2023-09-13 04:26:32 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-13 04:26:32 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-13 04:26:32 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-13 04:26:32 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-13 04:26:32 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-13 04:26:32 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-13 04:26:32 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-13 04:26:32 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-13 04:26:32 (4259) [INFO] 
* 2023-09-13 04:26:32 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-13 04:26:32 (4229) [INFO] 
* 2023-09-13 04:27:00 (4242) [INFO] 
* 2023-09-13 04:27:00 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-13 04:27:00 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-13 04:27:00 (4259) [INFO] 
* 2023-09-13 04:27:00 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-13 04:27:00 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-13 04:27:02 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-13 04:27:02 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-13 04:27:02 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-13 04:27:02 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-13 04:27: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-09-13 04:27:27 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-13 04:27:27 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2fKcsyA53T/ea_profile.json
* 2023-09-13 04:27:28 (2293) [INFO] Backed up EA4 profile to /tmp/2fKcsyA53T/ea_profile.json
* 2023-09-13 04:27:29 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-13 04:27:29 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-14 04:29:28 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-14 04:29:28 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-14 04:29:28 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-14 04:29:28 (4229) [INFO] 
* 2023-09-14 04:29:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-14 04:29:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-14 04:29:28 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-14 04:29:28 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-14 04:29:28 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-14 04:29:28 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-14 04:29:28 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-14 04:29:28 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-14 04:29:28 (4259) [INFO] 
* 2023-09-14 04:29:28 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-14 04:29:28 (4229) [INFO] 
* 2023-09-14 04:29:58 (4242) [INFO] 
* 2023-09-14 04:29:58 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-14 04:29:58 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-14 04:29:58 (4259) [INFO] 
* 2023-09-14 04:29:58 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-14 04:29:58 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-14 04:29:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-14 04:29:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-14 04:29:59 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-14 04:29:59 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-14 04:29: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-14 04:30:28 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-14 04:30:28 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/D6n3jDAVRn/ea_profile.json
* 2023-09-14 04:30:29 (2293) [INFO] Backed up EA4 profile to /tmp/D6n3jDAVRn/ea_profile.json
* 2023-09-14 04:30:30 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-14 04:30:30 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-15 04:26:31 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-15 04:26:31 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-15 04:26:31 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-15 04:26:31 (4229) [INFO] 
* 2023-09-15 04:26:32 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-15 04:26:32 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-15 04:26:32 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-15 04:26:32 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-15 04:26:32 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-15 04:26:32 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-15 04:26:32 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-15 04:26:32 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-15 04:26:32 (4259) [INFO] 
* 2023-09-15 04:26:32 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-15 04:26:32 (4229) [INFO] 
* 2023-09-15 04:27:02 (4242) [INFO] 
* 2023-09-15 04:27:02 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-15 04:27:02 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-15 04:27:02 (4259) [INFO] 
* 2023-09-15 04:27:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-15 04:27:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-15 04:27:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-15 04:27:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-15 04:27:04 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-15 04:27:04 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-15 04:27: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-09-15 04:27:30 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-15 04:27:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VzRGsQDSu6/ea_profile.json
* 2023-09-15 04:27:31 (2293) [INFO] Backed up EA4 profile to /tmp/VzRGsQDSu6/ea_profile.json
* 2023-09-15 04:27:32 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-15 04:27:32 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-16 04:27:23 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-16 04:27:23 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-16 04:27:23 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-16 04:27:23 (4229) [INFO] 
* 2023-09-16 04:27:23 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-16 04:27:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-16 04:27:23 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-16 04:27:23 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-16 04:27:23 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-16 04:27:23 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-16 04:27:23 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-16 04:27:23 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-16 04:27:23 (4259) [INFO] 
* 2023-09-16 04:27:23 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-16 04:27:23 (4229) [INFO] 
* 2023-09-16 04:27:53 (4242) [INFO] 
* 2023-09-16 04:27:53 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-16 04:27:53 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-16 04:27:53 (4259) [INFO] 
* 2023-09-16 04:27:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-16 04:27:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-16 04:27:55 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-16 04:27:55 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-16 04:27:55 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-16 04:27:55 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-16 04:27: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-09-16 04:28:22 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-16 04:28:22 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/A2cyqqQW6z/ea_profile.json
* 2023-09-16 04:28:23 (2293) [INFO] Backed up EA4 profile to /tmp/A2cyqqQW6z/ea_profile.json
* 2023-09-16 04:28:24 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-16 04:28:24 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-17 04:27:25 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-17 04:27:25 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-17 04:27:25 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-17 04:27:25 (4229) [INFO] 
* 2023-09-17 04:27:25 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-17 04:27:26 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-17 04:27:26 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-17 04:27:26 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-17 04:27:26 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-17 04:27:26 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-17 04:27:26 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-17 04:27:26 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-17 04:27:26 (4259) [INFO] 
* 2023-09-17 04:27:26 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-17 04:27:26 (4229) [INFO] 
* 2023-09-17 04:27:53 (4242) [INFO] 
* 2023-09-17 04:27:53 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-17 04:27:53 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-17 04:27:53 (4259) [INFO] 
* 2023-09-17 04:27:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-17 04:27:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-17 04:27:56 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-17 04:27:56 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-17 04:27:56 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-17 04:27:56 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-17 04:27: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-09-17 04:28:22 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-17 04:28:22 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gnmDGTqg7N/ea_profile.json
* 2023-09-17 04:28:23 (2293) [INFO] Backed up EA4 profile to /tmp/gnmDGTqg7N/ea_profile.json
* 2023-09-17 04:28:23 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-17 04:28:23 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-18 04:26:28 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-18 04:26:28 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-18 04:26:28 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-18 04:26:28 (4229) [INFO] 
* 2023-09-18 04:26:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-18 04:26:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-18 04:26:28 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-18 04:26:28 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-18 04:26:28 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-18 04:26:28 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-18 04:26:28 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-18 04:26:28 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-18 04:26:29 (4259) [INFO] 
* 2023-09-18 04:26:29 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-18 04:26:29 (4229) [INFO] 
* 2023-09-18 04:26:57 (4242) [INFO] 
* 2023-09-18 04:26:57 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-18 04:26:57 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-18 04:26:57 (4259) [INFO] 
* 2023-09-18 04:26:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-18 04:26:57 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-18 04:26:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-18 04:26:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-18 04:26:59 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-18 04:26:59 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-18 04:26: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-18 04:27:25 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-18 04:27:25 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1VdKXbXyPe/ea_profile.json
* 2023-09-18 04:27:26 (2293) [INFO] Backed up EA4 profile to /tmp/1VdKXbXyPe/ea_profile.json
* 2023-09-18 04:27:27 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-18 04:27:27 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-19 04:26:34 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-19 04:26:34 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-19 04:26:34 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-19 04:26:34 (4229) [INFO] 
* 2023-09-19 04:26:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-19 04:26:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-19 04:26:35 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-19 04:26:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-19 04:26:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-19 04:26:35 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-19 04:26:35 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-19 04:26:35 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-19 04:26:35 (4259) [INFO] 
* 2023-09-19 04:26:35 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-19 04:26:35 (4229) [INFO] 
* 2023-09-19 04:27:06 (4242) [INFO] 
* 2023-09-19 04:27:06 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-19 04:27:06 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-19 04:27:06 (4259) [INFO] 
* 2023-09-19 04:27:06 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-19 04:27:06 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-19 04:27:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-19 04:27:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-19 04:27:09 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-19 04:27:09 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-19 04:27: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-09-19 04:27:36 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-19 04:27:36 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bGxAXNUnJi/ea_profile.json
* 2023-09-19 04:27:37 (2293) [INFO] Backed up EA4 profile to /tmp/bGxAXNUnJi/ea_profile.json
* 2023-09-19 04:27:38 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-19 04:27:38 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-20 04:26:30 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-20 04:26:30 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-20 04:26:30 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-20 04:26:30 (4229) [INFO] 
* 2023-09-20 04:26:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-20 04:26:31 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-20 04:26:31 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-20 04:26:31 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-20 04:26:31 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-20 04:26:31 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-20 04:26:31 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-20 04:26:31 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-20 04:26:31 (4259) [INFO] 
* 2023-09-20 04:26:31 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-20 04:26:31 (4229) [INFO] 
* 2023-09-20 04:27:00 (4242) [INFO] 
* 2023-09-20 04:27:00 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-20 04:27:00 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-20 04:27:00 (4259) [INFO] 
* 2023-09-20 04:27:00 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-20 04:27:00 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-20 04:27:02 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-20 04:27:02 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-20 04:27:02 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-20 04:27:02 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-20 04:27: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-09-20 04:27:28 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-20 04:27:28 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zYMyKBiKYs/ea_profile.json
* 2023-09-20 04:27:29 (2293) [INFO] Backed up EA4 profile to /tmp/zYMyKBiKYs/ea_profile.json
* 2023-09-20 04:27:29 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-20 04:27:30 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-21 04:27:57 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-21 04:27:57 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-21 04:27:57 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-21 04:27:57 (4229) [INFO] 
* 2023-09-21 04:27:57 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-21 04:27:58 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-21 04:27:58 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-21 04:27:58 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-21 04:27:58 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-21 04:27:58 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-21 04:27:58 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-21 04:27:58 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-21 04:27:58 (4259) [INFO] 
* 2023-09-21 04:27:58 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-21 04:27:58 (4229) [INFO] 
* 2023-09-21 04:28:25 (4242) [INFO] 
* 2023-09-21 04:28:25 (4242) [INFO] kernel.x86_64                     3.10.0-1160.95.1.el7                   updates
* 2023-09-21 04:28:25 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-21 04:28:25 (4259) [INFO] 
* 2023-09-21 04:28:25 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-21 04:28:25 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-21 04:28:27 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-21 04:28:27 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-21 04:28:27 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-21 04:28:27 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-21 04:28: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-09-21 04:28:53 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-21 04:28:53 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mxdrWpq2CN/ea_profile.json
* 2023-09-21 04:28:54 (2293) [INFO] Backed up EA4 profile to /tmp/mxdrWpq2CN/ea_profile.json
* 2023-09-21 04:28:55 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-21 04:28:55 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-22 04:26:55 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-22 04:26:55 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-22 04:26:55 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-22 04:26:55 (4229) [INFO] 
* 2023-09-22 04:26:55 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-22 04:26:56 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-22 04:26:56 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-22 04:26:56 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-22 04:26:56 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-22 04:26:56 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-22 04:26:56 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-22 04:26:56 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-22 04:26:56 (4259) [INFO] 
* 2023-09-22 04:26:56 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-22 04:26:56 (4229) [INFO] 
* 2023-09-22 04:27:25 (4242) [INFO] 
* 2023-09-22 04:27:25 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-09-22 04:27:25 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-22 04:27:25 (4259) [INFO] 
* 2023-09-22 04:27:25 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-22 04:27:25 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-22 04:27:27 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-22 04:27:27 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-22 04:27:27 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-22 04:27:27 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-22 04:27: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-09-22 04:27:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-22 04:27:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BqqXpqmsOM/ea_profile.json
* 2023-09-22 04:27:53 (2293) [INFO] Backed up EA4 profile to /tmp/BqqXpqmsOM/ea_profile.json
* 2023-09-22 04:27:54 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-22 04:27:54 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-23 04:27:23 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-23 04:27:23 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-23 04:27:23 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-23 04:27:23 (4229) [INFO] 
* 2023-09-23 04:27:23 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-23 04:27:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-23 04:27:23 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-23 04:27:23 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-23 04:27:23 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-23 04:27:23 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-23 04:27:23 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-23 04:27:23 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-23 04:27:23 (4259) [INFO] 
* 2023-09-23 04:27:23 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-23 04:27:23 (4229) [INFO] 
* 2023-09-23 04:27:52 (4242) [INFO] 
* 2023-09-23 04:27:52 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-09-23 04:27:52 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-23 04:27:52 (4259) [INFO] 
* 2023-09-23 04:27:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-23 04:27:52 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-23 04:27:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-23 04:27:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-23 04:27:54 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-23 04:27:54 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-23 04:27: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-23 04:28:21 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-23 04:28:21 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PzNM3Vy7MP/ea_profile.json
* 2023-09-23 04:28:22 (2293) [INFO] Backed up EA4 profile to /tmp/PzNM3Vy7MP/ea_profile.json
* 2023-09-23 04:28:22 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-23 04:28:23 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-24 04:27:28 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-24 04:27:28 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-24 04:27:28 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-24 04:27:28 (4229) [INFO] 
* 2023-09-24 04:27:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-24 04:27:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-24 04:27:28 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-24 04:27:28 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-24 04:27:28 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-24 04:27:28 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-24 04:27:28 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-24 04:27:29 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-24 04:27:29 (4259) [INFO] 
* 2023-09-24 04:27:29 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-24 04:27:29 (4229) [INFO] 
* 2023-09-24 04:27:58 (4242) [INFO] 
* 2023-09-24 04:27:58 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-09-24 04:27:58 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-24 04:27:58 (4259) [INFO] 
* 2023-09-24 04:27:58 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-24 04:27:58 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-24 04:28:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-24 04:28:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-24 04:28:01 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-24 04:28:01 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-24 04:28: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-09-24 04:28:27 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-24 04:28:27 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j4KkCHVM52/ea_profile.json
* 2023-09-24 04:28:28 (2293) [INFO] Backed up EA4 profile to /tmp/j4KkCHVM52/ea_profile.json
* 2023-09-24 04:28:29 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-24 04:28:29 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-25 04:26:37 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-25 04:26:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-25 04:26:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-25 04:26:37 (4229) [INFO] 
* 2023-09-25 04:26:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-25 04:26:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-25 04:26:38 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-25 04:26:38 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-25 04:26:38 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-25 04:26:38 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-25 04:26:38 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-25 04:26:38 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-25 04:26:38 (4259) [INFO] 
* 2023-09-25 04:26:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-25 04:26:38 (4229) [INFO] 
* 2023-09-25 04:27:10 (4242) [INFO] 
* 2023-09-25 04:27:10 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-09-25 04:27:10 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-25 04:27:10 (4259) [INFO] 
* 2023-09-25 04:27:10 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-25 04:27:10 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-25 04:27:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-25 04:27:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-25 04:27:11 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-25 04:27:11 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-25 04:27: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-25 04:27:38 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-25 04:27:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VMK2talPjE/ea_profile.json
* 2023-09-25 04:27:39 (2293) [INFO] Backed up EA4 profile to /tmp/VMK2talPjE/ea_profile.json
* 2023-09-25 04:27:40 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-25 04:27:40 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-26 04:26:29 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-26 04:26:29 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-26 04:26:29 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-26 04:26:29 (4229) [INFO] 
* 2023-09-26 04:26:29 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-26 04:26:29 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-26 04:26:29 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-26 04:26:29 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-26 04:26:29 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-26 04:26:29 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-26 04:26:29 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-26 04:26:29 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-26 04:26:30 (4259) [INFO] 
* 2023-09-26 04:26:30 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-26 04:26:30 (4229) [INFO] 
* 2023-09-26 04:27:00 (4242) [INFO] 
* 2023-09-26 04:27:00 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-09-26 04:27:00 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-26 04:27:00 (4259) [INFO] 
* 2023-09-26 04:27:00 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-26 04:27:00 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-26 04:27:02 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-26 04:27:02 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-26 04:27:02 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-26 04:27:02 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-26 04:27: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-09-26 04:27:28 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-26 04:27:28 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lOpcL_aNTF/ea_profile.json
* 2023-09-26 04:27:30 (2293) [INFO] Backed up EA4 profile to /tmp/lOpcL_aNTF/ea_profile.json
* 2023-09-26 04:27:30 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-26 04:27:30 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-27 04:26:31 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-27 04:26:31 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-27 04:26:31 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-27 04:26:31 (4229) [INFO] 
* 2023-09-27 04:26:32 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-27 04:26:32 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-27 04:26:32 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-27 04:26:32 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-27 04:26:32 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-27 04:26:32 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-27 04:26:32 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-27 04:26:32 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-27 04:26:32 (4259) [INFO] 
* 2023-09-27 04:26:32 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-27 04:26:32 (4229) [INFO] 
* 2023-09-27 04:27:02 (4242) [INFO] 
* 2023-09-27 04:27:02 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-09-27 04:27:02 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-27 04:27:02 (4259) [INFO] 
* 2023-09-27 04:27:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-27 04:27:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-27 04:27:05 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-27 04:27:05 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-27 04:27:05 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-27 04:27:05 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-27 04:27: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-09-27 04:27:32 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-27 04:27:32 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uF_gWvheJ8/ea_profile.json
* 2023-09-27 04:27:33 (2293) [INFO] Backed up EA4 profile to /tmp/uF_gWvheJ8/ea_profile.json
* 2023-09-27 04:27:34 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-27 04:27:34 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-28 04:27:04 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-28 04:27:04 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-28 04:27:04 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-28 04:27:04 (4229) [INFO] 
* 2023-09-28 04:27:04 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-28 04:27:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-28 04:27:04 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-28 04:27:04 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-28 04:27:04 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-28 04:27:04 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-28 04:27:04 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-28 04:27:04 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-28 04:27:04 (4259) [INFO] 
* 2023-09-28 04:27:04 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-28 04:27:04 (4229) [INFO] 
* 2023-09-28 04:27:32 (4242) [INFO] 
* 2023-09-28 04:27:32 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-09-28 04:27:32 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-28 04:27:32 (4259) [INFO] 
* 2023-09-28 04:27:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-28 04:27:32 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-28 04:27:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-28 04:27:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-28 04:27:33 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-28 04:27:33 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-28 04:27: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-28 04:28:00 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-28 04:28:00 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/A_zjOvQTrM/ea_profile.json
* 2023-09-28 04:28:01 (2293) [INFO] Backed up EA4 profile to /tmp/A_zjOvQTrM/ea_profile.json
* 2023-09-28 04:28:02 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-28 04:28:02 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-29 04:26:34 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-29 04:26:34 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-29 04:26:34 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-29 04:26:34 (4229) [INFO] 
* 2023-09-29 04:26:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-29 04:26:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-29 04:26:35 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-29 04:26:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-29 04:26:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-29 04:26:35 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-29 04:26:35 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-29 04:26:35 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-29 04:26:35 (4259) [INFO] 
* 2023-09-29 04:26:35 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-29 04:26:35 (4229) [INFO] 
* 2023-09-29 04:27:15 (4242) [INFO] 
* 2023-09-29 04:27:15 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-09-29 04:27:15 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-29 04:27:15 (4259) [INFO] 
* 2023-09-29 04:27:15 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-29 04:27:15 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-29 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-29 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-29 04:27:18 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-29 04:27:18 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-29 04:27:18 (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 04:27:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-29 04:27:48 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r1Hy6NGF6l/ea_profile.json
* 2023-09-29 04:27:49 (2293) [INFO] Backed up EA4 profile to /tmp/r1Hy6NGF6l/ea_profile.json
* 2023-09-29 04:27:50 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-29 04:27:50 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-30 04:27:27 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-09-30 04:27:27 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-30 04:27:27 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-30 04:27:27 (4229) [INFO] 
* 2023-09-30 04:27:27 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-30 04:27:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-09-30 04:27:28 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-30 04:27:28 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-30 04:27:28 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-30 04:27:28 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-09-30 04:27:28 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-09-30 04:27:28 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-09-30 04:27:28 (4259) [INFO] 
* 2023-09-30 04:27:28 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-30 04:27:28 (4229) [INFO] 
* 2023-09-30 04:28:06 (4242) [INFO] 
* 2023-09-30 04:28:06 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-09-30 04:28:06 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-09-30 04:28:07 (4259) [INFO] 
* 2023-09-30 04:28:07 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-30 04:28:07 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-30 04:28:10 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-09-30 04:28:10 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-09-30 04:28:10 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-09-30 04:28:10 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-09-30 04:28: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-09-30 04:28:39 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-30 04:28:39 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EVS4hVDHNd/ea_profile.json
* 2023-09-30 04:28:40 (2293) [INFO] Backed up EA4 profile to /tmp/EVS4hVDHNd/ea_profile.json
* 2023-09-30 04:28:41 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-09-30 04:28:41 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-01 04:27:29 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-01 04:27:29 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-01 04:27:29 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-01 04:27:29 (4229) [INFO] 
* 2023-10-01 04:27:29 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-01 04:27:29 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-01 04:27:29 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-01 04:27:29 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-01 04:27:29 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-01 04:27:29 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-01 04:27:29 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-01 04:27:30 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-01 04:27:30 (4259) [INFO] 
* 2023-10-01 04:27:30 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-01 04:27:30 (4229) [INFO] 
* 2023-10-01 04:28:07 (4242) [INFO] 
* 2023-10-01 04:28:07 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-01 04:28:08 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-01 04:28:08 (4259) [INFO] 
* 2023-10-01 04:28:08 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-01 04:28:08 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-01 04:28:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-01 04:28:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-01 04:28:11 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-01 04:28:11 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-01 04:28: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-01 04:28:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-01 04:28:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lWq12QWce6/ea_profile.json
* 2023-10-01 04:28:42 (2293) [INFO] Backed up EA4 profile to /tmp/lWq12QWce6/ea_profile.json
* 2023-10-01 04:28:42 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-01 04:28:42 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-02 04:26:33 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-02 04:26:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-02 04:26:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-02 04:26:33 (4229) [INFO] 
* 2023-10-02 04:26:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-02 04:26:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-02 04:26:34 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-02 04:26:34 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-02 04:26:34 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-02 04:26:34 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-02 04:26:34 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-02 04:26:34 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-02 04:26:34 (4259) [INFO] 
* 2023-10-02 04:26:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-02 04:26:34 (4229) [INFO] 
* 2023-10-02 04:27:14 (4242) [INFO] 
* 2023-10-02 04:27:14 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-02 04:27:14 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-02 04:27:14 (4259) [INFO] 
* 2023-10-02 04:27:14 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-02 04:27:14 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-02 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-02 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-02 04:27:18 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-02 04:27:18 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-02 04:27:18 (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 04:27:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-02 04:27:46 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kcg3DOAws4/ea_profile.json
* 2023-10-02 04:27:47 (2293) [INFO] Backed up EA4 profile to /tmp/Kcg3DOAws4/ea_profile.json
* 2023-10-02 04:27:48 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-02 04:27:48 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-03 04:30:00 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-03 04:30:00 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-03 04:30:00 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-03 04:30:00 (4229) [INFO] 
* 2023-10-03 04:30:01 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-03 04:30:03 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-03 04:30:03 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-03 04:30:03 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-03 04:30:03 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-03 04:30:03 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-03 04:30:03 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-03 04:30:04 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-03 04:30:04 (4259) [INFO] 
* 2023-10-03 04:30:04 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-03 04:30:04 (4229) [INFO] 
* 2023-10-03 04:31:11 (4242) [INFO] 
* 2023-10-03 04:31:11 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-03 04:31:11 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-03 04:31:12 (4259) [INFO] 
* 2023-10-03 04:31:12 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-03 04:31:12 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-03 04:31:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-03 04:31:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-03 04:31:17 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-03 04:31:17 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-03 04:31:17 (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 04:32:19 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-03 04:32:19 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/U5Jd2pzF9K/ea_profile.json
* 2023-10-03 04:32:21 (2293) [INFO] Backed up EA4 profile to /tmp/U5Jd2pzF9K/ea_profile.json
* 2023-10-03 04:32:23 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-03 04:32:23 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-04 04:29:17 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-04 04:29:17 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-04 04:29:17 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-04 04:29:17 (4229) [INFO] 
* 2023-10-04 04:29:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-04 04:29:19 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-04 04:29:19 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-04 04:29:19 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-04 04:29:19 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-04 04:29:19 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-04 04:29:19 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-04 04:29:20 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-04 04:29:20 (4259) [INFO] 
* 2023-10-04 04:29:20 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-04 04:29:20 (4229) [INFO] 
* 2023-10-04 04:30:24 (4242) [INFO] 
* 2023-10-04 04:30:24 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-04 04:30:24 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-04 04:30:24 (4259) [INFO] 
* 2023-10-04 04:30:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-04 04:30:24 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-04 04:30:29 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-04 04:30:29 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-04 04:30:29 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-04 04:30:29 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-04 04:30:29 (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 04:31:16 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-04 04:31:16 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3a7cubYdSM/ea_profile.json
* 2023-10-04 04:31:18 (2293) [INFO] Backed up EA4 profile to /tmp/3a7cubYdSM/ea_profile.json
* 2023-10-04 04:31:20 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-04 04:31:20 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-05 04:28:35 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-05 04:28:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-05 04:28:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-05 04:28:35 (4229) [INFO] 
* 2023-10-05 04:28:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-05 04:28:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-05 04:28:36 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-05 04:28:36 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-05 04:28:36 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-05 04:28:36 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-05 04:28:36 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-05 04:28:37 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-05 04:28:37 (4259) [INFO] 
* 2023-10-05 04:28:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-05 04:28:37 (4229) [INFO] 
* 2023-10-05 04:29:44 (4242) [INFO] 
* 2023-10-05 04:29:44 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-05 04:29:44 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-05 04:29:44 (4259) [INFO] 
* 2023-10-05 04:29:44 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-05 04:29:44 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-05 04:29:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-05 04:29:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-05 04:29:48 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-05 04:29:48 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-05 04:29: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-10-05 04:30:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-05 04:30:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/e4FjBzRKMA/ea_profile.json
* 2023-10-05 04:30:49 (2293) [INFO] Backed up EA4 profile to /tmp/e4FjBzRKMA/ea_profile.json
* 2023-10-05 04:30:51 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-05 04:30:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-06 04:28:01 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-06 04:28:01 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-06 04:28:01 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-06 04:28:01 (4229) [INFO] 
* 2023-10-06 04:28:01 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-06 04:28:02 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-06 04:28:02 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-06 04:28:02 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-06 04:28:02 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-06 04:28:02 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-06 04:28:02 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-06 04:28:02 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-06 04:28:02 (4259) [INFO] 
* 2023-10-06 04:28:02 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-06 04:28:02 (4229) [INFO] 
* 2023-10-06 04:29:13 (4242) [INFO] 
* 2023-10-06 04:29:13 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-06 04:29:13 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-06 04:29:13 (4259) [INFO] 
* 2023-10-06 04:29:13 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-06 04:29:13 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-06 04:29:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-06 04:29:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-06 04:29:17 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-06 04:29:17 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-06 04:29:17 (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 04:30:19 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-06 04:30:19 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/urpqdKGIhl/ea_profile.json
* 2023-10-06 04:30:22 (2293) [INFO] Backed up EA4 profile to /tmp/urpqdKGIhl/ea_profile.json
* 2023-10-06 04:30:23 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-06 04:30:23 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-07 04:29:49 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-07 04:29:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-07 04:29:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-07 04:29:49 (4229) [INFO] 
* 2023-10-07 04:29:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-07 04:29:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-07 04:29:50 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-07 04:29:50 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-07 04:29:50 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-07 04:29:50 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-07 04:29:50 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-07 04:29:50 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-07 04:29:50 (4259) [INFO] 
* 2023-10-07 04:29:50 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-07 04:29:50 (4229) [INFO] 
* 2023-10-07 04:31:04 (4242) [INFO] 
* 2023-10-07 04:31:04 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-07 04:31:04 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-07 04:31:04 (4259) [INFO] 
* 2023-10-07 04:31:04 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-07 04:31:04 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-07 04:31:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-07 04:31:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-07 04:31:12 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-07 04:31:12 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-07 04:31: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-10-07 04:32:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-07 04:32:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AjBYOliUhH/ea_profile.json
* 2023-10-07 04:32:13 (2293) [INFO] Backed up EA4 profile to /tmp/AjBYOliUhH/ea_profile.json
* 2023-10-07 04:32:14 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-07 04:32:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-08 04:29:42 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-08 04:29:42 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-08 04:29:42 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-08 04:29:42 (4229) [INFO] 
* 2023-10-08 04:29:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-08 04:29:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-08 04:29:43 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-08 04:29:43 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-08 04:29:43 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-08 04:29:43 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-08 04:29:43 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-08 04:29:43 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-08 04:29:43 (4259) [INFO] 
* 2023-10-08 04:29:43 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-08 04:29:43 (4229) [INFO] 
* 2023-10-08 04:30:55 (4242) [INFO] 
* 2023-10-08 04:30:55 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-08 04:30:55 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-08 04:30:55 (4259) [INFO] 
* 2023-10-08 04:30:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-08 04:30:55 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-08 04:31:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-08 04:31:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-08 04:31:04 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-08 04:31:04 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-08 04:31: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-10-08 04:32:03 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-08 04:32:03 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IU9TijQasn/ea_profile.json
* 2023-10-08 04:32:06 (2293) [INFO] Backed up EA4 profile to /tmp/IU9TijQasn/ea_profile.json
* 2023-10-08 04:32:07 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-08 04:32:07 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-09 04:26:43 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-09 04:26:43 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-09 04:26:43 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-09 04:26:43 (4229) [INFO] 
* 2023-10-09 04:26:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-09 04:26:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-09 04:26:43 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-09 04:26:43 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-09 04:26:43 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-09 04:26:43 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-09 04:26:43 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-09 04:26:44 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-09 04:26:44 (4259) [INFO] 
* 2023-10-09 04:26:44 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-09 04:26:44 (4229) [INFO] 
* 2023-10-09 04:27:23 (4242) [INFO] 
* 2023-10-09 04:27:23 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-09 04:27:23 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-09 04:27:23 (4259) [INFO] 
* 2023-10-09 04:27:23 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-09 04:27:23 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-09 04:27:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-09 04:27:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-09 04:27:33 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-09 04:27:33 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-09 04:27: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-09 04:28:01 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-09 04:28:01 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/srkAp2II9o/ea_profile.json
* 2023-10-09 04:28:02 (2293) [INFO] Backed up EA4 profile to /tmp/srkAp2II9o/ea_profile.json
* 2023-10-09 04:28:03 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-09 04:28:03 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-10 04:26:48 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-10 04:26:48 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-10 04:26:48 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-10 04:26:48 (4229) [INFO] 
* 2023-10-10 04:26:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-10 04:26:49 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-10 04:26:49 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-10 04:26:49 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-10 04:26:49 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-10 04:26:49 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-10 04:26:49 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-10 04:26:49 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-10 04:26:49 (4259) [INFO] 
* 2023-10-10 04:26:49 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-10 04:26:49 (4229) [INFO] 
* 2023-10-10 04:27:19 (4242) [INFO] 
* 2023-10-10 04:27:19 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-10 04:27:19 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-10 04:27:19 (4259) [INFO] 
* 2023-10-10 04:27:19 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-10 04:27:19 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-10 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-10 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-10 04:27:23 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-10 04:27:23 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-10 04:27: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-10-10 04:27:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-10 04:27:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QW17aiboiS/ea_profile.json
* 2023-10-10 04:27:53 (2293) [INFO] Backed up EA4 profile to /tmp/QW17aiboiS/ea_profile.json
* 2023-10-10 04:27:54 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-10 04:27:54 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-11 04:26:42 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-11 04:26:42 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-11 04:26:42 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-11 04:26:42 (4229) [INFO] 
* 2023-10-11 04:26:42 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-11 04:26:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-11 04:26:43 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-11 04:26:43 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-11 04:26:43 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-11 04:26:43 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-11 04:26:43 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-11 04:26:43 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-11 04:26:43 (4259) [INFO] 
* 2023-10-11 04:26:43 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-11 04:26:43 (4229) [INFO] 
* 2023-10-11 04:27:12 (4242) [INFO] 
* 2023-10-11 04:27:12 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-11 04:27:12 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-11 04:27:12 (4259) [INFO] 
* 2023-10-11 04:27:12 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-11 04:27:12 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-11 04:27:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-11 04:27:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-11 04:27:17 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-11 04:27:17 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-11 04:27:17 (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 04:27:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-11 04:27:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gvQMmvd4ya/ea_profile.json
* 2023-10-11 04:27:44 (2293) [INFO] Backed up EA4 profile to /tmp/gvQMmvd4ya/ea_profile.json
* 2023-10-11 04:27:45 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-11 04:27:45 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-12 04:26:45 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-12 04:26:45 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-12 04:26:45 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-12 04:26:45 (4229) [INFO] 
* 2023-10-12 04:26:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-12 04:26:45 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-12 04:26:45 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-12 04:26:45 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-12 04:26:45 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-12 04:26:45 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-12 04:26:45 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-12 04:26:45 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-12 04:26:45 (4259) [INFO] 
* 2023-10-12 04:26:45 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-12 04:26:45 (4229) [INFO] 
* 2023-10-12 04:27:16 (4242) [INFO] 
* 2023-10-12 04:27:16 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-12 04:27:16 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-12 04:27:16 (4259) [INFO] 
* 2023-10-12 04:27:16 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-12 04:27:16 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-12 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-12 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-12 04:27:23 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-12 04:27:23 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-12 04:27: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-10-12 04:27:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-12 04:27:51 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_JlWQ4a0Sc/ea_profile.json
* 2023-10-12 04:27:52 (2293) [INFO] Backed up EA4 profile to /tmp/_JlWQ4a0Sc/ea_profile.json
* 2023-10-12 04:27:53 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-12 04:27:53 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-13 04:28:07 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-13 04:28:07 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-13 04:28:07 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-13 04:28:07 (4229) [INFO] 
* 2023-10-13 04:28:07 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-13 04:28:07 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-13 04:28:07 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-13 04:28:07 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-13 04:28:07 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-13 04:28:07 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-13 04:28:07 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-13 04:28:07 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-13 04:28:07 (4259) [INFO] 
* 2023-10-13 04:28:07 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-13 04:28:07 (4229) [INFO] 
* 2023-10-13 04:28:37 (4242) [INFO] 
* 2023-10-13 04:28:37 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-13 04:28:37 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-13 04:28:37 (4259) [INFO] 
* 2023-10-13 04:28:37 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-13 04:28:37 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-13 04:28:41 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-13 04:28:41 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-13 04:28:41 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-13 04:28:41 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-13 04:28:41 (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 04:29:08 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-13 04:29:08 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QrL8NASu9c/ea_profile.json
* 2023-10-13 04:29:10 (2293) [INFO] Backed up EA4 profile to /tmp/QrL8NASu9c/ea_profile.json
* 2023-10-13 04:29:11 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-13 04:29:11 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-14 04:27:43 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-14 04:27:43 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-14 04:27:43 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-14 04:27:43 (4229) [INFO] 
* 2023-10-14 04:27:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-14 04:27:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-14 04:27:43 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-14 04:27:43 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-14 04:27:43 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-14 04:27:43 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-14 04:27:43 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-14 04:27:44 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-14 04:27:44 (4259) [INFO] 
* 2023-10-14 04:27:44 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-14 04:27:44 (4229) [INFO] 
* 2023-10-14 04:28:14 (4242) [INFO] 
* 2023-10-14 04:28:14 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-14 04:28:14 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-14 04:28:14 (4259) [INFO] 
* 2023-10-14 04:28:14 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-14 04:28:14 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-14 04:28:20 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-14 04:28:20 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-14 04:28:20 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-14 04:28:20 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-14 04:28:20 (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 04:28:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-14 04:28:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eVEk4WYd1O/ea_profile.json
* 2023-10-14 04:28:50 (2293) [INFO] Backed up EA4 profile to /tmp/eVEk4WYd1O/ea_profile.json
* 2023-10-14 04:28:51 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-14 04:28:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-15 04:27:44 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-15 04:27:44 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-15 04:27:44 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-15 04:27:44 (4229) [INFO] 
* 2023-10-15 04:27:44 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-15 04:27:44 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-15 04:27:44 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-15 04:27:44 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-15 04:27:44 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-15 04:27:44 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-15 04:27:44 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-15 04:27:44 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-15 04:27:44 (4259) [INFO] 
* 2023-10-15 04:27:44 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-15 04:27:44 (4229) [INFO] 
* 2023-10-15 04:28:15 (4242) [INFO] 
* 2023-10-15 04:28:15 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-15 04:28:15 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-15 04:28:15 (4259) [INFO] 
* 2023-10-15 04:28:15 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-15 04:28:15 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-15 04:28:22 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-15 04:28:22 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-15 04:28:22 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-15 04:28:22 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-15 04:28: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-10-15 04:28:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-15 04:28:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FkPZtWbY79/ea_profile.json
* 2023-10-15 04:28:51 (2293) [INFO] Backed up EA4 profile to /tmp/FkPZtWbY79/ea_profile.json
* 2023-10-15 04:28:52 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-15 04:28:52 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-16 04:26:39 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-16 04:26:39 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-16 04:26:39 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-16 04:26:39 (4229) [INFO] 
* 2023-10-16 04:26:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-16 04:26:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-16 04:26:39 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-16 04:26:39 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-16 04:26:39 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-16 04:26:39 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-16 04:26:39 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-16 04:26:39 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-16 04:26:39 (4259) [INFO] 
* 2023-10-16 04:26:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-16 04:26:39 (4229) [INFO] 
* 2023-10-16 04:27:08 (4242) [INFO] 
* 2023-10-16 04:27:08 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-16 04:27:08 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-16 04:27:08 (4259) [INFO] 
* 2023-10-16 04:27:08 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-16 04:27:08 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-16 04:27:15 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-16 04:27:15 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-16 04:27:15 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-16 04:27:15 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-16 04:27: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-16 04:27:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-16 04:27:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/18lyUj3wSE/ea_profile.json
* 2023-10-16 04:27:43 (2293) [INFO] Backed up EA4 profile to /tmp/18lyUj3wSE/ea_profile.json
* 2023-10-16 04:27:44 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-16 04:27:44 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-17 04:26:46 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-17 04:26:46 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-17 04:26:46 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-17 04:26:46 (4229) [INFO] 
* 2023-10-17 04:26:47 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-17 04:26:47 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-17 04:26:47 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-17 04:26:47 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-17 04:26:47 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-17 04:26:47 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-17 04:26:47 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-17 04:26:47 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-17 04:26:47 (4259) [INFO] 
* 2023-10-17 04:26:47 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-17 04:26:47 (4229) [INFO] 
* 2023-10-17 04:27:18 (4242) [INFO] 
* 2023-10-17 04:27:18 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-17 04:27:18 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-17 04:27:18 (4259) [INFO] 
* 2023-10-17 04:27:18 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-17 04:27:18 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-17 04:27:28 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-17 04:27:28 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-17 04:27:28 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-17 04:27:28 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-17 04:27:28 (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 04:27:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-17 04:27:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uMkkdronJf/ea_profile.json
* 2023-10-17 04:28:01 (2293) [INFO] Backed up EA4 profile to /tmp/uMkkdronJf/ea_profile.json
* 2023-10-17 04:28:03 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-17 04:28:03 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-18 04:26:43 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-18 04:26:43 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-18 04:26:43 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-18 04:26:43 (4229) [INFO] 
* 2023-10-18 04:26:44 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-18 04:26:44 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-18 04:26:44 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-18 04:26:44 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-18 04:26:44 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-18 04:26:44 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-18 04:26:44 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-18 04:26:44 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-18 04:26:44 (4259) [INFO] 
* 2023-10-18 04:26:44 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-18 04:26:44 (4229) [INFO] 
* 2023-10-18 04:27:13 (4242) [INFO] 
* 2023-10-18 04:27:13 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-18 04:27:13 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-18 04:27:13 (4259) [INFO] 
* 2023-10-18 04:27:13 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-18 04:27:13 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-18 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-18 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-18 04:27:23 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-18 04:27:23 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-18 04:27: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-10-18 04:27:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-18 04:27:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dPyA4rsNQS/ea_profile.json
* 2023-10-18 04:27:56 (2293) [INFO] Backed up EA4 profile to /tmp/dPyA4rsNQS/ea_profile.json
* 2023-10-18 04:27:57 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-18 04:27:57 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-19 04:29:00 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-19 04:29:00 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-19 04:29:00 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-19 04:29:00 (4229) [INFO] 
* 2023-10-19 04:29:00 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-19 04:29:00 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-19 04:29:00 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-19 04:29:00 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-19 04:29:00 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-19 04:29:00 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-19 04:29:00 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-19 04:29:01 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-19 04:29:01 (4259) [INFO] 
* 2023-10-19 04:29:01 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-19 04:29:01 (4229) [INFO] 
* 2023-10-19 04:29:31 (4242) [INFO] 
* 2023-10-19 04:29:31 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-19 04:29:31 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-19 04:29:31 (4259) [INFO] 
* 2023-10-19 04:29:31 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-19 04:29:31 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-19 04:29:32 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-19 04:29:32 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-19 04:29:32 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-19 04:29:32 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-19 04:29: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-19 04:29:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-19 04:29:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/b6_MbLtuAa/ea_profile.json
* 2023-10-19 04:30:00 (2293) [INFO] Backed up EA4 profile to /tmp/b6_MbLtuAa/ea_profile.json
* 2023-10-19 04:30:01 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-19 04:30:01 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-20 04:26:46 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-20 04:26:46 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-20 04:26:46 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-20 04:26:46 (4229) [INFO] 
* 2023-10-20 04:26:46 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-20 04:26:46 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-20 04:26:46 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-20 04:26:46 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-20 04:26:46 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-20 04:26:46 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-20 04:26:46 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-20 04:26:46 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-20 04:26:46 (4259) [INFO] 
* 2023-10-20 04:26:46 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-20 04:26:46 (4229) [INFO] 
* 2023-10-20 04:27:16 (4242) [INFO] 
* 2023-10-20 04:27:16 (4242) [INFO] kernel.x86_64                     3.10.0-1160.99.1.el7                   updates
* 2023-10-20 04:27:16 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-20 04:27:16 (4259) [INFO] 
* 2023-10-20 04:27:16 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-20 04:27:16 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-20 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-20 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-20 04:27:18 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-20 04:27:18 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-20 04:27:18 (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 04:27:45 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-20 04:27:45 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/azahej0cts/ea_profile.json
* 2023-10-20 04:27:46 (2293) [INFO] Backed up EA4 profile to /tmp/azahej0cts/ea_profile.json
* 2023-10-20 04:27:47 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-20 04:27:47 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-21 04:28:13 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-21 04:28:13 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-21 04:28:13 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-21 04:28:13 (4229) [INFO] 
* 2023-10-21 04:28:14 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-21 04:28:14 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-21 04:28:14 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-21 04:28:14 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-21 04:28:14 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-21 04:28:14 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-21 04:28:14 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-21 04:28:14 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-21 04:28:14 (4259) [INFO] 
* 2023-10-21 04:28:14 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-21 04:28:14 (4229) [INFO] 
* 2023-10-21 04:28:42 (4242) [INFO] 
* 2023-10-21 04:28:42 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-21 04:28:42 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-21 04:28:43 (4259) [INFO] 
* 2023-10-21 04:28:43 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-21 04:28:43 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-21 04:28:44 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-21 04:28:44 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-21 04:28:44 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-21 04:28:44 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-21 04:28: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-10-21 04:29:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-21 04:29:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bcZCBxx9tP/ea_profile.json
* 2023-10-21 04:29:13 (2293) [INFO] Backed up EA4 profile to /tmp/bcZCBxx9tP/ea_profile.json
* 2023-10-21 04:29:14 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-21 04:29:14 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-22 04:27:25 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-22 04:27:25 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-22 04:27:25 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-22 04:27:25 (4229) [INFO] 
* 2023-10-22 04:27:25 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-22 04:27:25 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-22 04:27:25 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-22 04:27:25 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-22 04:27:25 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-22 04:27:25 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-22 04:27:25 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-22 04:27:25 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-22 04:27:25 (4259) [INFO] 
* 2023-10-22 04:27:25 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-22 04:27:25 (4229) [INFO] 
* 2023-10-22 04:27:55 (4242) [INFO] 
* 2023-10-22 04:27:55 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-22 04:27:55 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-22 04:27:56 (4259) [INFO] 
* 2023-10-22 04:27:56 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-22 04:27:56 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-22 04:27:58 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-22 04:27:58 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-22 04:27:58 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-22 04:27:58 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-22 04:27: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-10-22 04:28:25 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-22 04:28:25 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XivZBr7_Es/ea_profile.json
* 2023-10-22 04:28:26 (2293) [INFO] Backed up EA4 profile to /tmp/XivZBr7_Es/ea_profile.json
* 2023-10-22 04:28:27 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-22 04:28:27 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-23 04:26:40 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-23 04:26:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-23 04:26:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-23 04:26:40 (4229) [INFO] 
* 2023-10-23 04:26:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-23 04:26:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-23 04:26:40 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-23 04:26:40 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-23 04:26:40 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-23 04:26:40 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-23 04:26:40 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-23 04:26:41 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-23 04:26:41 (4259) [INFO] 
* 2023-10-23 04:26:41 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-23 04:26:41 (4229) [INFO] 
* 2023-10-23 04:27:14 (4242) [INFO] 
* 2023-10-23 04:27:14 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-23 04:27:14 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-23 04:27:14 (4259) [INFO] 
* 2023-10-23 04:27:14 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-23 04:27:14 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-23 04:27:16 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-23 04:27:16 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-23 04:27:16 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-23 04:27:16 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-23 04:27:16 (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 04:27:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-23 04:27:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XM3vtbuj1i/ea_profile.json
* 2023-10-23 04:27:44 (2293) [INFO] Backed up EA4 profile to /tmp/XM3vtbuj1i/ea_profile.json
* 2023-10-23 04:27:44 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-23 04:27:45 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-24 04:26:35 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-24 04:26:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-24 04:26:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-24 04:26:35 (4229) [INFO] 
* 2023-10-24 04:26:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-24 04:26:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-24 04:26:35 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-24 04:26:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-24 04:26:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-24 04:26:35 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-24 04:26:35 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-24 04:26:35 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-24 04:26:35 (4259) [INFO] 
* 2023-10-24 04:26:35 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-24 04:26:35 (4229) [INFO] 
* 2023-10-24 04:27:06 (4242) [INFO] 
* 2023-10-24 04:27:06 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-24 04:27:06 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-24 04:27:06 (4259) [INFO] 
* 2023-10-24 04:27:06 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-24 04:27:06 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-24 04:27:07 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-24 04:27:07 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-24 04:27:07 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-24 04:27:07 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-24 04:27: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-24 04:27:34 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-24 04:27:34 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ny1PaQYrxO/ea_profile.json
* 2023-10-24 04:27:35 (2293) [INFO] Backed up EA4 profile to /tmp/ny1PaQYrxO/ea_profile.json
* 2023-10-24 04:27:36 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-24 04:27:36 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-25 04:26:28 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-25 04:26:28 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-25 04:26:28 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-25 04:26:28 (4229) [INFO] 
* 2023-10-25 04:26:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-25 04:26:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-25 04:26:28 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-25 04:26:28 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-25 04:26:28 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-25 04:26:28 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-25 04:26:28 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-25 04:26:28 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-25 04:26:28 (4259) [INFO] 
* 2023-10-25 04:26:28 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-25 04:26:28 (4229) [INFO] 
* 2023-10-25 04:26:58 (4242) [INFO] 
* 2023-10-25 04:26:58 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-25 04:26:58 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-25 04:26:58 (4259) [INFO] 
* 2023-10-25 04:26:58 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-25 04:26:58 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-25 04:27:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-25 04:27:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-25 04:27:01 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-25 04:27:01 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-25 04:27: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-25 04:27:27 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-25 04:27:27 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OmMKkN4387/ea_profile.json
* 2023-10-25 04:27:28 (2293) [INFO] Backed up EA4 profile to /tmp/OmMKkN4387/ea_profile.json
* 2023-10-25 04:27:29 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-25 04:27:29 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-26 04:27:24 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-26 04:27:24 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-26 04:27:24 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-26 04:27:24 (4229) [INFO] 
* 2023-10-26 04:27:24 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-26 04:27:24 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-26 04:27:24 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-26 04:27:24 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-26 04:27:24 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-26 04:27:24 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-26 04:27:24 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-26 04:27:24 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-26 04:27:24 (4259) [INFO] 
* 2023-10-26 04:27:24 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-26 04:27:24 (4229) [INFO] 
* 2023-10-26 04:27:55 (4242) [INFO] 
* 2023-10-26 04:27:55 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-26 04:27:55 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-26 04:27:56 (4259) [INFO] 
* 2023-10-26 04:27:56 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-26 04:27:56 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-26 04:27:57 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-26 04:27:57 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-26 04:27:57 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-26 04:27:57 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-26 04:27: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-10-26 04:28:24 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-26 04:28:24 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oCTRfimRBr/ea_profile.json
* 2023-10-26 04:28:25 (2293) [INFO] Backed up EA4 profile to /tmp/oCTRfimRBr/ea_profile.json
* 2023-10-26 04:28:26 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-26 04:28:26 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-27 04:26:30 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-27 04:26:30 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-27 04:26:30 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-27 04:26:30 (4229) [INFO] 
* 2023-10-27 04:26:30 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-27 04:26:30 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-27 04:26:30 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-27 04:26:30 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-27 04:26:30 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-27 04:26:30 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-27 04:26:30 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-27 04:26:30 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-27 04:26:30 (4259) [INFO] 
* 2023-10-27 04:26:30 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-27 04:26:30 (4229) [INFO] 
* 2023-10-27 04:27:01 (4242) [INFO] 
* 2023-10-27 04:27:01 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-27 04:27:01 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-27 04:27:01 (4259) [INFO] 
* 2023-10-27 04:27:01 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-27 04:27:01 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-27 04:27:02 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-27 04:27:02 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-27 04:27:02 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-27 04:27:02 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-27 04:27: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-10-27 04:27:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-27 04:27:29 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4d3w6TVsy0/ea_profile.json
* 2023-10-27 04:27:30 (2293) [INFO] Backed up EA4 profile to /tmp/4d3w6TVsy0/ea_profile.json
* 2023-10-27 04:27:31 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-27 04:27:31 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-28 04:28:19 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-28 04:28:19 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-28 04:28:19 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-28 04:28:19 (4229) [INFO] 
* 2023-10-28 04:28:20 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-28 04:28:20 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-28 04:28:20 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-28 04:28:20 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-28 04:28:20 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-28 04:28:20 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-28 04:28:20 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-28 04:28:20 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-28 04:28:20 (4259) [INFO] 
* 2023-10-28 04:28:20 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-28 04:28:20 (4229) [INFO] 
* 2023-10-28 04:28:52 (4242) [INFO] 
* 2023-10-28 04:28:52 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-28 04:28:52 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-28 04:28:52 (4259) [INFO] 
* 2023-10-28 04:28:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-28 04:28:52 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-28 04:28:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-28 04:28:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-28 04:28:54 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-28 04:28:54 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-28 04:28: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-10-28 04:29:22 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-28 04:29:22 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_MipsSNYst/ea_profile.json
* 2023-10-28 04:29:23 (2293) [INFO] Backed up EA4 profile to /tmp/_MipsSNYst/ea_profile.json
* 2023-10-28 04:29:24 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-28 04:29:24 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-29 04:27:31 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-29 04:27:31 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-29 04:27:31 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-29 04:27:31 (4229) [INFO] 
* 2023-10-29 04:27:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-29 04:27:31 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-29 04:27:31 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-29 04:27:31 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-29 04:27:31 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-29 04:27:31 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-29 04:27:31 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-29 04:27:32 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-29 04:27:32 (4259) [INFO] 
* 2023-10-29 04:27:32 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-29 04:27:32 (4229) [INFO] 
* 2023-10-29 04:28:16 (4242) [INFO] 
* 2023-10-29 04:28:16 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-29 04:28:16 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-29 04:28:16 (4259) [INFO] 
* 2023-10-29 04:28:16 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-29 04:28:16 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-29 04:28:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-29 04:28:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-29 04:28:18 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-29 04:28:18 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-29 04:28:18 (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 04:28:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-29 04:28:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/msYHLQXyeY/ea_profile.json
* 2023-10-29 04:28:50 (2293) [INFO] Backed up EA4 profile to /tmp/msYHLQXyeY/ea_profile.json
* 2023-10-29 04:28:51 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-29 04:28:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-30 04:26:35 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-30 04:26:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-30 04:26:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-30 04:26:35 (4229) [INFO] 
* 2023-10-30 04:26:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-30 04:26:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-30 04:26:36 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-30 04:26:36 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-30 04:26:36 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-30 04:26:36 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-30 04:26:36 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-30 04:26:36 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-30 04:26:36 (4259) [INFO] 
* 2023-10-30 04:26:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-30 04:26:36 (4229) [INFO] 
* 2023-10-30 04:27:20 (4242) [INFO] 
* 2023-10-30 04:27:20 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-30 04:27:20 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-30 04:27:20 (4259) [INFO] 
* 2023-10-30 04:27:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-30 04:27:20 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-30 04:27:22 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-30 04:27:22 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-30 04:27:22 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-30 04:27:22 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-30 04:27: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-10-30 04:27:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-30 04:27:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WD1C6t1cWI/ea_profile.json
* 2023-10-30 04:27:54 (2293) [INFO] Backed up EA4 profile to /tmp/WD1C6t1cWI/ea_profile.json
* 2023-10-30 04:27:54 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-30 04:27:54 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-31 04:26:40 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-10-31 04:26:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-31 04:26:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-31 04:26:40 (4229) [INFO] 
* 2023-10-31 04:26:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-31 04:26:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-10-31 04:26:40 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-31 04:26:40 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-31 04:26:40 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-31 04:26:40 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-10-31 04:26:40 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-10-31 04:26:41 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-10-31 04:26:41 (4259) [INFO] 
* 2023-10-31 04:26:41 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-31 04:26:41 (4229) [INFO] 
* 2023-10-31 04:27:21 (4242) [INFO] 
* 2023-10-31 04:27:21 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-10-31 04:27:21 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-10-31 04:27:21 (4259) [INFO] 
* 2023-10-31 04:27:21 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-31 04:27:21 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-31 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-10-31 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-10-31 04:27:23 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-10-31 04:27:23 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-10-31 04:27: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-10-31 04:27:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-31 04:27:55 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LedaA2Z7NN/ea_profile.json
* 2023-10-31 04:27:56 (2293) [INFO] Backed up EA4 profile to /tmp/LedaA2Z7NN/ea_profile.json
* 2023-10-31 04:27:57 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-10-31 04:27:57 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-01 04:26:37 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-01 04:26:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-01 04:26:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-01 04:26:37 (4229) [INFO] 
* 2023-11-01 04:26:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-01 04:26:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-01 04:26:38 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-01 04:26:38 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-01 04:26:38 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-01 04:26:38 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-01 04:26:38 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-01 04:26:38 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-01 04:26:38 (4259) [INFO] 
* 2023-11-01 04:26:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-01 04:26:38 (4229) [INFO] 
* 2023-11-01 04:27:21 (4242) [INFO] 
* 2023-11-01 04:27:21 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-01 04:27:21 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-01 04:27:21 (4259) [INFO] 
* 2023-11-01 04:27:21 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-01 04:27:21 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-01 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-01 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-01 04:27:23 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-01 04:27:23 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-01 04:27: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-01 04:27:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-01 04:27:51 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X5DRLzg1XC/ea_profile.json
* 2023-11-01 04:27:52 (2293) [INFO] Backed up EA4 profile to /tmp/X5DRLzg1XC/ea_profile.json
* 2023-11-01 04:27:53 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-01 04:27:53 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-02 04:26:31 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-02 04:26:31 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-02 04:26:31 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-02 04:26:31 (4229) [INFO] 
* 2023-11-02 04:26:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-02 04:26:31 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-02 04:26:31 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-02 04:26:31 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-02 04:26:31 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-02 04:26:31 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-02 04:26:31 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-02 04:26:31 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-02 04:26:31 (4259) [INFO] 
* 2023-11-02 04:26:31 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-02 04:26:31 (4229) [INFO] 
* 2023-11-02 04:27:02 (4242) [INFO] 
* 2023-11-02 04:27:02 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-02 04:27:02 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-02 04:27:02 (4259) [INFO] 
* 2023-11-02 04:27:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-02 04:27:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-02 04:27:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-02 04:27:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-02 04:27:04 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-02 04:27:04 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-02 04:27: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-02 04:27:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-02 04:27:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZEXAQUTokj/ea_profile.json
* 2023-11-02 04:27:34 (2293) [INFO] Backed up EA4 profile to /tmp/ZEXAQUTokj/ea_profile.json
* 2023-11-02 04:27:35 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-02 04:27:35 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-03 04:26:41 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-03 04:26:41 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-03 04:26:41 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-03 04:26:41 (4229) [INFO] 
* 2023-11-03 04:26:41 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-03 04:26:41 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-03 04:26:41 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-03 04:26:41 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-03 04:26:41 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-03 04:26:41 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-03 04:26:41 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-03 04:26:42 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-03 04:26:42 (4259) [INFO] 
* 2023-11-03 04:26:42 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-03 04:26:42 (4229) [INFO] 
* 2023-11-03 04:27:22 (4242) [INFO] 
* 2023-11-03 04:27:22 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-03 04:27:22 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-03 04:27:22 (4259) [INFO] 
* 2023-11-03 04:27:22 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-03 04:27:22 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-03 04:27:25 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-03 04:27:25 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-03 04:27:25 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-03 04:27:25 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-03 04:27: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-03 04:27:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-03 04:27:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eTU7KkzztR/ea_profile.json
* 2023-11-03 04:27:55 (2293) [INFO] Backed up EA4 profile to /tmp/eTU7KkzztR/ea_profile.json
* 2023-11-03 04:27:55 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-03 04:27:55 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-04 04:27:37 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-04 04:27:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-04 04:27:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-04 04:27:37 (4229) [INFO] 
* 2023-11-04 04:27:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-04 04:27:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-04 04:27:38 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-04 04:27:38 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-04 04:27:38 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-04 04:27:38 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-04 04:27:38 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-04 04:27:38 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-04 04:27:38 (4259) [INFO] 
* 2023-11-04 04:27:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-04 04:27:38 (4229) [INFO] 
* 2023-11-04 04:28:18 (4242) [INFO] 
* 2023-11-04 04:28:18 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-04 04:28:18 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-04 04:28:19 (4259) [INFO] 
* 2023-11-04 04:28:19 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-04 04:28:19 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-04 04:28:21 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-04 04:28:21 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-04 04:28:21 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-04 04:28:21 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-04 04:28: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-11-04 04:28:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-04 04:28:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OeAQ0mAKHE/ea_profile.json
* 2023-11-04 04:28:50 (2293) [INFO] Backed up EA4 profile to /tmp/OeAQ0mAKHE/ea_profile.json
* 2023-11-04 04:28:51 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-04 04:28:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-05 04:27:24 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-05 04:27:24 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-05 04:27:24 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-05 04:27:24 (4229) [INFO] 
* 2023-11-05 04:27:24 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-05 04:27:25 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-05 04:27:25 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-05 04:27:25 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-05 04:27:25 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-05 04:27:25 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-05 04:27:25 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-05 04:27:25 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-05 04:27:25 (4259) [INFO] 
* 2023-11-05 04:27:25 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-05 04:27:25 (4229) [INFO] 
* 2023-11-05 04:27:56 (4242) [INFO] 
* 2023-11-05 04:27:56 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-05 04:27:56 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-05 04:27:57 (4259) [INFO] 
* 2023-11-05 04:27:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-05 04:27:57 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-05 04:27:58 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-05 04:27:58 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-05 04:27:58 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-05 04:27:58 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-05 04:27: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-05 04:28:26 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-05 04:28:26 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NnBQDLmf8n/ea_profile.json
* 2023-11-05 04:28:27 (2293) [INFO] Backed up EA4 profile to /tmp/NnBQDLmf8n/ea_profile.json
* 2023-11-05 04:28:28 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-05 04:28:28 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-06 04:26:31 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-06 04:26:31 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-06 04:26:31 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-06 04:26:31 (4229) [INFO] 
* 2023-11-06 04:26:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-06 04:26:32 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-06 04:26:32 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-06 04:26:32 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-06 04:26:32 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-06 04:26:32 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-06 04:26:32 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-06 04:26:32 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-06 04:26:32 (4259) [INFO] 
* 2023-11-06 04:26:32 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-06 04:26:32 (4229) [INFO] 
* 2023-11-06 04:27:12 (4242) [INFO] 
* 2023-11-06 04:27:12 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-06 04:27:12 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-06 04:27:12 (4259) [INFO] 
* 2023-11-06 04:27:12 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-06 04:27:12 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-06 04:27:14 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-06 04:27:14 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-06 04:27:14 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-06 04:27:14 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-06 04:27:14 (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 04:27:45 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-06 04:27:45 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CmNeTFf89A/ea_profile.json
* 2023-11-06 04:27:46 (2293) [INFO] Backed up EA4 profile to /tmp/CmNeTFf89A/ea_profile.json
* 2023-11-06 04:27:47 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-06 04:27:47 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-07 04:26:35 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-07 04:26:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-07 04:26:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-07 04:26:35 (4229) [INFO] 
* 2023-11-07 04:26:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-07 04:26:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-07 04:26:35 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-07 04:26:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-07 04:26:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-07 04:26:35 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-07 04:26:35 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-07 04:26:36 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-07 04:26:36 (4259) [INFO] 
* 2023-11-07 04:26:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-07 04:26:36 (4229) [INFO] 
* 2023-11-07 04:27:15 (4242) [INFO] 
* 2023-11-07 04:27:15 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-07 04:27:15 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-07 04:27:16 (4259) [INFO] 
* 2023-11-07 04:27:16 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-07 04:27:16 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-07 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-07 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-07 04:27:18 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-07 04:27:18 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-07 04:27:18 (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 04:27:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-07 04:27:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/16XHUGhSZ_/ea_profile.json
* 2023-11-07 04:27:48 (2293) [INFO] Backed up EA4 profile to /tmp/16XHUGhSZ_/ea_profile.json
* 2023-11-07 04:27:48 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-07 04:27:49 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-08 04:26:29 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-08 04:26:29 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-08 04:26:29 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-08 04:26:29 (4229) [INFO] 
* 2023-11-08 04:26:29 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-08 04:26:29 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-08 04:26:29 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-08 04:26:29 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-08 04:26:29 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-08 04:26:29 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-08 04:26:29 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-08 04:26:29 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-08 04:26:29 (4259) [INFO] 
* 2023-11-08 04:26:29 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-08 04:26:29 (4229) [INFO] 
* 2023-11-08 04:26:37 (4242) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 502 - Bad Gateway
* 2023-11-08 04:26:37 (4242) [INFO] Trying other mirror.
* 2023-11-08 04:27:10 (4242) [INFO] 
* 2023-11-08 04:27:10 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-08 04:27:10 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-08 04:27:10 (4259) [INFO] 
* 2023-11-08 04:27:10 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-08 04:27:10 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-08 04:27:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-08 04:27:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-08 04:27:12 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-08 04:27:12 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-08 04:27: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-11-08 04:27:38 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-08 04:27:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GQCnkC_pPA/ea_profile.json
* 2023-11-08 04:27:39 (2293) [INFO] Backed up EA4 profile to /tmp/GQCnkC_pPA/ea_profile.json
* 2023-11-08 04:27:39 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-08 04:27:39 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-09 04:28:01 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-09 04:28:01 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-09 04:28:01 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-09 04:28:01 (4229) [INFO] 
* 2023-11-09 04:28:01 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-09 04:28:02 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-09 04:28:02 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-09 04:28:02 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-09 04:28:02 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-09 04:28:02 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-09 04:28:02 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-09 04:28:02 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-09 04:28:02 (4259) [INFO] 
* 2023-11-09 04:28:02 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-09 04:28:02 (4229) [INFO] 
* 2023-11-09 04:28:40 (4242) [INFO] 
* 2023-11-09 04:28:40 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-09 04:28:40 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-09 04:28:40 (4259) [INFO] 
* 2023-11-09 04:28:40 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-09 04:28:40 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-09 04:28:42 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-09 04:28:42 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-09 04:28:42 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-09 04:28:42 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-09 04:28: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-09 04:29:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-09 04:29:10 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8MSXt8W2Ig/ea_profile.json
* 2023-11-09 04:29:11 (2293) [INFO] Backed up EA4 profile to /tmp/8MSXt8W2Ig/ea_profile.json
* 2023-11-09 04:29:12 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-09 04:29:12 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-10 04:26:33 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-10 04:26:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-10 04:26:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-10 04:26:33 (4229) [INFO] 
* 2023-11-10 04:26:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-10 04:26:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-10 04:26:33 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-10 04:26:33 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-10 04:26:33 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-10 04:26:33 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-10 04:26:33 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-10 04:26:34 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-10 04:26:34 (4259) [INFO] 
* 2023-11-10 04:26:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-10 04:26:34 (4229) [INFO] 
* 2023-11-10 04:27:01 (4242) [INFO] 
* 2023-11-10 04:27:01 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-10 04:27:01 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-10 04:27:01 (4259) [INFO] 
* 2023-11-10 04:27:01 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-10 04:27:01 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-10 04:27:03 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-10 04:27:03 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-10 04:27:03 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-10 04:27:03 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-10 04:27: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-10 04:27:30 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-10 04:27:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rjzjh_ApDy/ea_profile.json
* 2023-11-10 04:27:31 (2293) [INFO] Backed up EA4 profile to /tmp/rjzjh_ApDy/ea_profile.json
* 2023-11-10 04:27:32 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-10 04:27:32 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-11 04:27:43 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-11 04:27:43 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-11 04:27:43 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-11 04:27:43 (4229) [INFO] 
* 2023-11-11 04:27:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-11 04:27:44 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-11 04:27:44 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-11 04:27:44 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-11 04:27:44 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-11 04:27:44 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-11 04:27:44 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-11 04:27:44 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-11 04:27:44 (4259) [INFO] 
* 2023-11-11 04:27:44 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-11 04:27:44 (4229) [INFO] 
* 2023-11-11 04:28:25 (4242) [INFO] 
* 2023-11-11 04:28:25 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-11 04:28:25 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-11 04:28:26 (4259) [INFO] 
* 2023-11-11 04:28:26 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-11 04:28:26 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-11 04:28:29 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-11 04:28:29 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-11 04:28:29 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-11 04:28:29 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-11 04:28:29 (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 04:28:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-11 04:28:56 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m82iqMKhBf/ea_profile.json
* 2023-11-11 04:28:57 (2293) [INFO] Backed up EA4 profile to /tmp/m82iqMKhBf/ea_profile.json
* 2023-11-11 04:28:58 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-11 04:28:58 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-12 04:27:28 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-12 04:27:28 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-12 04:27:28 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-12 04:27:28 (4229) [INFO] 
* 2023-11-12 04:27:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-12 04:27:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-12 04:27:28 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-12 04:27:28 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-12 04:27:28 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-12 04:27:28 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-12 04:27:28 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-12 04:27:29 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-12 04:27:29 (4259) [INFO] 
* 2023-11-12 04:27:29 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-12 04:27:29 (4229) [INFO] 
* 2023-11-12 04:28:09 (4242) [INFO] 
* 2023-11-12 04:28:09 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-12 04:28:09 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-12 04:28:10 (4259) [INFO] 
* 2023-11-12 04:28:10 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-12 04:28:10 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-12 04:28:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-12 04:28:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-12 04:28:12 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-12 04:28:12 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-12 04:28: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-11-12 04:28:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-12 04:28:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X5UxQ2SsgZ/ea_profile.json
* 2023-11-12 04:28:41 (2293) [INFO] Backed up EA4 profile to /tmp/X5UxQ2SsgZ/ea_profile.json
* 2023-11-12 04:28:42 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-12 04:28:42 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-13 04:26:35 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-13 04:26:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-13 04:26:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-13 04:26:35 (4229) [INFO] 
* 2023-11-13 04:26:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-13 04:26:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-13 04:26:35 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-13 04:26:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-13 04:26:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-13 04:26:35 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-13 04:26:35 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-13 04:26:36 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-13 04:26:36 (4259) [INFO] 
* 2023-11-13 04:26:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-13 04:26:36 (4229) [INFO] 
* 2023-11-13 04:27:14 (4242) [INFO] 
* 2023-11-13 04:27:14 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-13 04:27:14 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-13 04:27:15 (4259) [INFO] 
* 2023-11-13 04:27:15 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-13 04:27:15 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-13 04:27:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-13 04:27:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-13 04:27:17 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-13 04:27:17 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-13 04:27:17 (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 04:27:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-13 04:27:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RMe2oXskI0/ea_profile.json
* 2023-11-13 04:27:44 (2293) [INFO] Backed up EA4 profile to /tmp/RMe2oXskI0/ea_profile.json
* 2023-11-13 04:27:45 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-13 04:27:45 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-14 04:27:26 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-14 04:27:26 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-14 04:27:26 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-14 04:27:26 (4229) [INFO] 
* 2023-11-14 04:27:26 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-14 04:27:27 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-14 04:27:27 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-14 04:27:27 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-14 04:27:27 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-14 04:27:27 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-14 04:27:27 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-14 04:27:27 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-14 04:27:27 (4259) [INFO] 
* 2023-11-14 04:27:27 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-14 04:27:27 (4229) [INFO] 
* 2023-11-14 04:28:05 (4242) [INFO] 
* 2023-11-14 04:28:05 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-14 04:28:05 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-14 04:28:06 (4259) [INFO] 
* 2023-11-14 04:28:06 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-14 04:28:06 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-14 04:28:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-14 04:28:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-14 04:28:08 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-14 04:28:08 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-14 04:28: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-14 04:28:34 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-14 04:28:34 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/45VeyXD_Uc/ea_profile.json
* 2023-11-14 04:28:35 (2293) [INFO] Backed up EA4 profile to /tmp/45VeyXD_Uc/ea_profile.json
* 2023-11-14 04:28:36 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-14 04:28:36 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-15 04:26:37 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-15 04:26:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-15 04:26:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-15 04:26:37 (4229) [INFO] 
* 2023-11-15 04:26:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-15 04:26:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-15 04:26:38 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-15 04:26:38 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-15 04:26:38 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-15 04:26:38 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-15 04:26:38 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-15 04:26:38 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-15 04:26:38 (4259) [INFO] 
* 2023-11-15 04:26:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-15 04:26:38 (4229) [INFO] 
* 2023-11-15 04:27:17 (4242) [INFO] 
* 2023-11-15 04:27:17 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-15 04:27:17 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-15 04:27:17 (4259) [INFO] 
* 2023-11-15 04:27:17 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-15 04:27:17 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-15 04:27:21 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-15 04:27:21 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-15 04:27:21 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-15 04:27:21 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-15 04:27: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-11-15 04:27:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-15 04:27:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/A8CIZtAph3/ea_profile.json
* 2023-11-15 04:27:50 (2293) [INFO] Backed up EA4 profile to /tmp/A8CIZtAph3/ea_profile.json
* 2023-11-15 04:27:51 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-15 04:27:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-16 04:29:58 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-16 04:29:58 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-16 04:29:58 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-16 04:29:58 (4229) [INFO] 
* 2023-11-16 04:29:58 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-16 04:29:59 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-16 04:29:59 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-16 04:29:59 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-16 04:29:59 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-16 04:29:59 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-16 04:29:59 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-16 04:29:59 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-16 04:29:59 (4259) [INFO] 
* 2023-11-16 04:29:59 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-16 04:29:59 (4229) [INFO] 
* 2023-11-16 04:30:35 (4242) [INFO] 
* 2023-11-16 04:30:35 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-16 04:30:35 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-16 04:30:35 (4259) [INFO] 
* 2023-11-16 04:30:35 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-16 04:30:35 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-16 04:30:37 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-16 04:30:37 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-16 04:30:37 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-16 04:30:37 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-16 04:30: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-11-16 04:31:06 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-16 04:31:07 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OngeyYoDar/ea_profile.json
* 2023-11-16 04:31:08 (2293) [INFO] Backed up EA4 profile to /tmp/OngeyYoDar/ea_profile.json
* 2023-11-16 04:31:09 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-16 04:31:09 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-17 04:26:55 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-17 04:26:55 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-17 04:26:55 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-17 04:26:55 (4229) [INFO] 
* 2023-11-17 04:26:55 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-17 04:26:55 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-17 04:26:55 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-17 04:26:55 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-17 04:26:55 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-17 04:26:55 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-17 04:26:55 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-17 04:26:56 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-17 04:26:56 (4259) [INFO] 
* 2023-11-17 04:26:56 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-17 04:26:56 (4229) [INFO] 
* 2023-11-17 04:27:34 (4242) [INFO] 
* 2023-11-17 04:27:34 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-17 04:27:34 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-17 04:27:35 (4259) [INFO] 
* 2023-11-17 04:27:35 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-17 04:27:35 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-17 04:27:37 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-17 04:27:37 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-17 04:27:37 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-17 04:27:37 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-17 04:27: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-11-17 04:28:03 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-17 04:28:03 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Atq8w2tTkH/ea_profile.json
* 2023-11-17 04:28:04 (2293) [INFO] Backed up EA4 profile to /tmp/Atq8w2tTkH/ea_profile.json
* 2023-11-17 04:28:05 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-17 04:28:05 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-18 04:27:39 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-18 04:27:39 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-18 04:27:39 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-18 04:27:39 (4229) [INFO] 
* 2023-11-18 04:27:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-18 04:27:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-18 04:27:40 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-18 04:27:40 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-18 04:27:40 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-18 04:27:40 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-18 04:27:40 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-18 04:27:40 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-18 04:27:40 (4259) [INFO] 
* 2023-11-18 04:27:40 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-18 04:27:40 (4229) [INFO] 
* 2023-11-18 04:28:19 (4242) [INFO] 
* 2023-11-18 04:28:19 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-18 04:28:19 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-18 04:28:19 (4259) [INFO] 
* 2023-11-18 04:28:19 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-18 04:28:19 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-18 04:28:22 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-18 04:28:22 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-18 04:28:22 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-18 04:28:22 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-18 04:28: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-11-18 04:28:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-18 04:28:48 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XA6GJpTMpJ/ea_profile.json
* 2023-11-18 04:28:49 (2293) [INFO] Backed up EA4 profile to /tmp/XA6GJpTMpJ/ea_profile.json
* 2023-11-18 04:28:50 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-18 04:28:50 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-19 04:28:10 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-19 04:28:10 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-19 04:28:10 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-19 04:28:10 (4229) [INFO] 
* 2023-11-19 04:28:10 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-19 04:28:10 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-19 04:28:10 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-19 04:28:10 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-19 04:28:10 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-19 04:28:10 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-19 04:28:10 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-19 04:28:11 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-19 04:28:11 (4259) [INFO] 
* 2023-11-19 04:28:11 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-19 04:28:11 (4229) [INFO] 
* 2023-11-19 04:28:48 (4242) [INFO] 
* 2023-11-19 04:28:48 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-19 04:28:48 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-19 04:28:48 (4259) [INFO] 
* 2023-11-19 04:28:48 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-19 04:28:48 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-19 04:28:51 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-19 04:28:51 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-19 04:28:51 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-19 04:28:51 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-19 04:28: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-19 04:29:17 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-19 04:29:17 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xo3h_7dFOA/ea_profile.json
* 2023-11-19 04:29:18 (2293) [INFO] Backed up EA4 profile to /tmp/xo3h_7dFOA/ea_profile.json
* 2023-11-19 04:29:19 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-19 04:29:19 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-20 04:26:35 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-20 04:26:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-20 04:26:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-20 04:26:35 (4229) [INFO] 
* 2023-11-20 04:26:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-20 04:26:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-20 04:26:35 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-20 04:26:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-20 04:26:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-20 04:26:35 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-20 04:26:35 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-20 04:26:35 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-20 04:26:36 (4259) [INFO] 
* 2023-11-20 04:26:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-20 04:26:36 (4229) [INFO] 
* 2023-11-20 04:27:20 (4242) [INFO] 
* 2023-11-20 04:27:20 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-20 04:27:20 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-20 04:27:20 (4259) [INFO] 
* 2023-11-20 04:27:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-20 04:27:20 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-20 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-20 04:27:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-20 04:27:23 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-20 04:27:23 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-20 04:27: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-20 04:27:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-20 04:27:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1Gk97ZYahl/ea_profile.json
* 2023-11-20 04:27:50 (2293) [INFO] Backed up EA4 profile to /tmp/1Gk97ZYahl/ea_profile.json
* 2023-11-20 04:27:51 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-20 04:27:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-21 04:26:45 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-21 04:26:45 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-21 04:26:45 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-21 04:26:45 (4229) [INFO] 
* 2023-11-21 04:26:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-21 04:26:46 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-21 04:26:46 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-21 04:26:46 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-21 04:26:46 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-21 04:26:46 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-21 04:26:46 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-21 04:26:46 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-21 04:26:46 (4259) [INFO] 
* 2023-11-21 04:26:46 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-21 04:26:46 (4229) [INFO] 
* 2023-11-21 04:27:26 (4242) [INFO] 
* 2023-11-21 04:27:26 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-21 04:27:26 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-21 04:27:26 (4259) [INFO] 
* 2023-11-21 04:27:26 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-21 04:27:26 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-21 04:27:28 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-21 04:27:28 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-21 04:27:28 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-21 04:27:28 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-21 04:27:28 (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 04:27:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-21 04:27:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nzvMl9t5ik/ea_profile.json
* 2023-11-21 04:28:00 (2293) [INFO] Backed up EA4 profile to /tmp/nzvMl9t5ik/ea_profile.json
* 2023-11-21 04:28:01 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-21 04:28:01 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-22 04:26:34 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-22 04:26:34 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-22 04:26:34 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-22 04:26:34 (4229) [INFO] 
* 2023-11-22 04:26:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-22 04:26:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-22 04:26:34 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-22 04:26:34 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-22 04:26:34 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-22 04:26:34 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-22 04:26:34 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-22 04:26:35 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-22 04:26:35 (4259) [INFO] 
* 2023-11-22 04:26:35 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-22 04:26:35 (4229) [INFO] 
* 2023-11-22 04:27:16 (4242) [INFO] 
* 2023-11-22 04:27:16 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-22 04:27:16 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-22 04:27:17 (4259) [INFO] 
* 2023-11-22 04:27:17 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-22 04:27:17 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-22 04:27:19 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-22 04:27:19 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-22 04:27:19 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-22 04:27:19 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-22 04:27:19 (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 04:27:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-22 04:27:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/z_YM04TncN/ea_profile.json
* 2023-11-22 04:27:48 (2293) [INFO] Backed up EA4 profile to /tmp/z_YM04TncN/ea_profile.json
* 2023-11-22 04:27:48 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-22 04:27:49 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-23 04:26:29 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-23 04:26:29 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-23 04:26:29 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-23 04:26:29 (4229) [INFO] 
* 2023-11-23 04:26:29 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-23 04:26:29 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-23 04:26:29 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-23 04:26:29 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-23 04:26:29 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-23 04:26:29 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-23 04:26:29 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-23 04:26:29 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-23 04:26:29 (4259) [INFO] 
* 2023-11-23 04:26:29 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-23 04:26:29 (4229) [INFO] 
* 2023-11-23 04:26:59 (4242) [INFO] 
* 2023-11-23 04:26:59 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-23 04:26:59 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-23 04:26:59 (4259) [INFO] 
* 2023-11-23 04:26:59 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-23 04:26:59 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-23 04:27:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-23 04:27:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-23 04:27:01 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-23 04:27:01 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-23 04:27: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-23 04:27:26 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-23 04:27:26 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oIq2PEQbTU/ea_profile.json
* 2023-11-23 04:27:27 (2293) [INFO] Backed up EA4 profile to /tmp/oIq2PEQbTU/ea_profile.json
* 2023-11-23 04:27:28 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-23 04:27:28 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-24 04:26:32 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-24 04:26:32 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-24 04:26:32 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-24 04:26:32 (4229) [INFO] 
* 2023-11-24 04:26:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-24 04:26:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-24 04:26:33 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-24 04:26:33 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-24 04:26:33 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-24 04:26:33 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-24 04:26:33 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-24 04:26:33 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-24 04:26:33 (4259) [INFO] 
* 2023-11-24 04:26:33 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-24 04:26:33 (4229) [INFO] 
* 2023-11-24 04:27:15 (4242) [INFO] 
* 2023-11-24 04:27:15 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-24 04:27:15 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-24 04:27:15 (4259) [INFO] 
* 2023-11-24 04:27:15 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-24 04:27:15 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-24 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-24 04:27:18 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-24 04:27:18 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-24 04:27:18 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-24 04:27:18 (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 04:27:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-24 04:27:46 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DeU3DlRIrt/ea_profile.json
* 2023-11-24 04:27:48 (2293) [INFO] Backed up EA4 profile to /tmp/DeU3DlRIrt/ea_profile.json
* 2023-11-24 04:27:48 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-24 04:27:48 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-25 04:27:36 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-25 04:27:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-25 04:27:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-25 04:27:36 (4229) [INFO] 
* 2023-11-25 04:27:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-25 04:27:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-25 04:27:37 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-25 04:27:37 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-25 04:27:37 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-25 04:27:37 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-25 04:27:37 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-25 04:27:38 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-25 04:27:38 (4259) [INFO] 
* 2023-11-25 04:27:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-25 04:27:38 (4229) [INFO] 
* 2023-11-25 04:28:17 (4242) [INFO] 
* 2023-11-25 04:28:17 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-25 04:28:17 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-25 04:28:17 (4259) [INFO] 
* 2023-11-25 04:28:17 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-25 04:28:17 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-25 04:28:20 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-25 04:28:20 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-25 04:28:20 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-25 04:28:20 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-25 04:28:20 (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 04:28:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-25 04:28:46 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MVL5caFy5f/ea_profile.json
* 2023-11-25 04:28:47 (2293) [INFO] Backed up EA4 profile to /tmp/MVL5caFy5f/ea_profile.json
* 2023-11-25 04:28:47 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-25 04:28:48 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-26 04:27:36 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-26 04:27:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-26 04:27:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-26 04:27:36 (4229) [INFO] 
* 2023-11-26 04:27:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-26 04:27:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-26 04:27:36 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-26 04:27:36 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-26 04:27:36 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-26 04:27:36 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-26 04:27:36 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-26 04:27:37 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-26 04:27:37 (4259) [INFO] 
* 2023-11-26 04:27:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-26 04:27:37 (4229) [INFO] 
* 2023-11-26 04:28:18 (4242) [INFO] 
* 2023-11-26 04:28:18 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-26 04:28:18 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-26 04:28:18 (4259) [INFO] 
* 2023-11-26 04:28:18 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-26 04:28:18 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-26 04:28:21 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-26 04:28:21 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-26 04:28:21 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-26 04:28:21 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-26 04:28: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-11-26 04:28:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-26 04:28:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o7j8Y4JD4a/ea_profile.json
* 2023-11-26 04:28:48 (2293) [INFO] Backed up EA4 profile to /tmp/o7j8Y4JD4a/ea_profile.json
* 2023-11-26 04:28:48 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-26 04:28:48 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-27 04:26:34 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-27 04:26:34 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-27 04:26:34 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-27 04:26:34 (4229) [INFO] 
* 2023-11-27 04:26:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-27 04:26:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-27 04:26:34 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-27 04:26:34 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-27 04:26:34 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-27 04:26:34 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-27 04:26:34 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-27 04:26:34 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-27 04:26:34 (4259) [INFO] 
* 2023-11-27 04:26:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-27 04:26:34 (4229) [INFO] 
* 2023-11-27 04:27:15 (4242) [INFO] 
* 2023-11-27 04:27:15 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-27 04:27:15 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-27 04:27:15 (4259) [INFO] 
* 2023-11-27 04:27:15 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-27 04:27:15 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-27 04:27:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-27 04:27:17 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-27 04:27:17 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-27 04:27:17 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-27 04:27:17 (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 04:27:44 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-27 04:27:44 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/x8A73Q3Tu0/ea_profile.json
* 2023-11-27 04:27:45 (2293) [INFO] Backed up EA4 profile to /tmp/x8A73Q3Tu0/ea_profile.json
* 2023-11-27 04:27:46 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-27 04:27:46 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-28 04:26:29 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-28 04:26:29 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-28 04:26:29 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-28 04:26:29 (4229) [INFO] 
* 2023-11-28 04:26:30 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-28 04:26:30 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-28 04:26:30 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-28 04:26:30 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-28 04:26:30 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-28 04:26:30 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-28 04:26:30 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-28 04:26:30 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-28 04:26:30 (4259) [INFO] 
* 2023-11-28 04:26:30 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-28 04:26:30 (4229) [INFO] 
* 2023-11-28 04:27:09 (4242) [INFO] 
* 2023-11-28 04:27:09 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-28 04:27:09 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-28 04:27:09 (4259) [INFO] 
* 2023-11-28 04:27:09 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-28 04:27:09 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-28 04:27:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-28 04:27:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-28 04:27:12 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-28 04:27:12 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-28 04:27: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-11-28 04:27:39 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-28 04:27:39 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m7eAzi9qfp/ea_profile.json
* 2023-11-28 04:27:40 (2293) [INFO] Backed up EA4 profile to /tmp/m7eAzi9qfp/ea_profile.json
* 2023-11-28 04:27:41 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-28 04:27:41 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-29 04:26:38 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-29 04:26:38 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-29 04:26:38 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-29 04:26:38 (4229) [INFO] 
* 2023-11-29 04:26:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-29 04:26:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-29 04:26:38 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-29 04:26:38 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-29 04:26:38 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-29 04:26:38 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-29 04:26:38 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-29 04:26:39 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-29 04:26:39 (4259) [INFO] 
* 2023-11-29 04:26:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-29 04:26:39 (4229) [INFO] 
* 2023-11-29 04:27:18 (4242) [INFO] 
* 2023-11-29 04:27:18 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-29 04:27:18 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-29 04:27:18 (4259) [INFO] 
* 2023-11-29 04:27:18 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-29 04:27:18 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-29 04:27:20 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-29 04:27:20 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-29 04:27:20 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-29 04:27:20 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-29 04:27:20 (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 04:27:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-29 04:27:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/16Z9YtWecE/ea_profile.json
* 2023-11-29 04:27:48 (2293) [INFO] Backed up EA4 profile to /tmp/16Z9YtWecE/ea_profile.json
* 2023-11-29 04:27:49 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-29 04:27:49 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-30 04:26:33 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-11-30 04:26:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-30 04:26:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-30 04:26:33 (4229) [INFO] 
* 2023-11-30 04:26:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-30 04:26:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-11-30 04:26:33 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-30 04:26:33 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-30 04:26:33 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-30 04:26:33 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-11-30 04:26:33 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-11-30 04:26:34 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-11-30 04:26:34 (4259) [INFO] 
* 2023-11-30 04:26:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-30 04:26:34 (4229) [INFO] 
* 2023-11-30 04:27:05 (4242) [INFO] 
* 2023-11-30 04:27:05 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-11-30 04:27:05 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-11-30 04:27:06 (4259) [INFO] 
* 2023-11-30 04:27:06 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-30 04:27:06 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-30 04:27:09 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-11-30 04:27:09 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-11-30 04:27:09 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-11-30 04:27:09 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-11-30 04:27: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-30 04:27:34 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-30 04:27:34 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3kI4uk3Am3/ea_profile.json
* 2023-11-30 04:27:36 (2293) [INFO] Backed up EA4 profile to /tmp/3kI4uk3Am3/ea_profile.json
* 2023-11-30 04:27:36 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-11-30 04:27:36 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-01 04:28:25 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-01 04:28:25 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-01 04:28:25 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-01 04:28:25 (4229) [INFO] 
* 2023-12-01 04:28:26 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-01 04:28:26 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-01 04:28:26 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-01 04:28:26 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-01 04:28:26 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-01 04:28:26 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-01 04:28:26 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-01 04:28:26 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-01 04:28:26 (4259) [INFO] 
* 2023-12-01 04:28:26 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-01 04:28:26 (4229) [INFO] 
* 2023-12-01 04:29:02 (4242) [INFO] 
* 2023-12-01 04:29:02 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-01 04:29:02 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-01 04:29:02 (4259) [INFO] 
* 2023-12-01 04:29:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-01 04:29:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-01 04:29:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-01 04:29:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-01 04:29:04 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-01 04:29:04 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-01 04:29: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-01 04:29:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-01 04:29:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uJ6kuqQiSN/ea_profile.json
* 2023-12-01 04:29:34 (2293) [INFO] Backed up EA4 profile to /tmp/uJ6kuqQiSN/ea_profile.json
* 2023-12-01 04:29:35 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-01 04:29:35 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-02 04:27:32 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-02 04:27:32 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-02 04:27:32 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-02 04:27:32 (4229) [INFO] 
* 2023-12-02 04:27:32 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-02 04:27:32 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-02 04:27:32 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-02 04:27:32 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-02 04:27:32 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-02 04:27:32 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-02 04:27:32 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-02 04:27:33 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-02 04:27:33 (4259) [INFO] 
* 2023-12-02 04:27:33 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-02 04:27:33 (4229) [INFO] 
* 2023-12-02 04:28:11 (4242) [INFO] 
* 2023-12-02 04:28:11 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-02 04:28:11 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-02 04:28:11 (4259) [INFO] 
* 2023-12-02 04:28:11 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-02 04:28:11 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-02 04:28:13 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-02 04:28:13 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-02 04:28:13 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-02 04:28:13 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-02 04:28: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-12-02 04:28:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-02 04:28:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JsIUBtA5tV/ea_profile.json
* 2023-12-02 04:28:41 (2293) [INFO] Backed up EA4 profile to /tmp/JsIUBtA5tV/ea_profile.json
* 2023-12-02 04:28:41 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-02 04:28:42 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-03 04:27:33 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-03 04:27:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-03 04:27:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-03 04:27:33 (4229) [INFO] 
* 2023-12-03 04:27:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-03 04:27:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-03 04:27:34 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-03 04:27:34 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-03 04:27:34 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-03 04:27:34 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-03 04:27:34 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-03 04:27:34 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-03 04:27:34 (4259) [INFO] 
* 2023-12-03 04:27:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-03 04:27:34 (4229) [INFO] 
* 2023-12-03 04:28:13 (4242) [INFO] 
* 2023-12-03 04:28:13 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-03 04:28:13 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-03 04:28:13 (4259) [INFO] 
* 2023-12-03 04:28:13 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-03 04:28:13 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-03 04:28:16 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-03 04:28:16 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-03 04:28:16 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-03 04:28:16 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-03 04:28:16 (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 04:28:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-03 04:28:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Tys63u236s/ea_profile.json
* 2023-12-03 04:28:44 (2293) [INFO] Backed up EA4 profile to /tmp/Tys63u236s/ea_profile.json
* 2023-12-03 04:28:45 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-03 04:28:45 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-04 04:26:33 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-04 04:26:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-04 04:26:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-04 04:26:33 (4229) [INFO] 
* 2023-12-04 04:26:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-04 04:26:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-04 04:26:34 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-04 04:26:34 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-04 04:26:34 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-04 04:26:34 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-04 04:26:34 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-04 04:26:34 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-04 04:26:34 (4259) [INFO] 
* 2023-12-04 04:26:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-04 04:26:34 (4229) [INFO] 
* 2023-12-04 04:27:11 (4242) [INFO] 
* 2023-12-04 04:27:11 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-04 04:27:11 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-04 04:27:11 (4259) [INFO] 
* 2023-12-04 04:27:11 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-04 04:27:11 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-04 04:27:14 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-04 04:27:14 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-04 04:27:14 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-04 04:27:14 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-04 04:27:14 (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 04:27:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-04 04:27:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6Bq7vazgpW/ea_profile.json
* 2023-12-04 04:27:43 (2293) [INFO] Backed up EA4 profile to /tmp/6Bq7vazgpW/ea_profile.json
* 2023-12-04 04:27:43 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-04 04:27:44 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-05 04:26:33 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-05 04:26:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-05 04:26:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-05 04:26:33 (4229) [INFO] 
* 2023-12-05 04:26:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-05 04:26:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-05 04:26:34 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-05 04:26:34 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-05 04:26:34 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-05 04:26:34 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-05 04:26:34 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-05 04:26:34 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-05 04:26:34 (4259) [INFO] 
* 2023-12-05 04:26:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-05 04:26:34 (4229) [INFO] 
* 2023-12-05 04:27:11 (4242) [INFO] 
* 2023-12-05 04:27:11 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-05 04:27:11 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-05 04:27:11 (4259) [INFO] 
* 2023-12-05 04:27:11 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-05 04:27:11 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-05 04:27:14 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-05 04:27:14 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-05 04:27:14 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-05 04:27:14 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-05 04:27:14 (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 04:27:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-05 04:27:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/L9vKAx1NFV/ea_profile.json
* 2023-12-05 04:27:41 (2293) [INFO] Backed up EA4 profile to /tmp/L9vKAx1NFV/ea_profile.json
* 2023-12-05 04:27:42 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-05 04:27:42 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-06 04:26:31 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-06 04:26:31 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-06 04:26:31 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-06 04:26:31 (4229) [INFO] 
* 2023-12-06 04:26:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-06 04:26:31 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-06 04:26:31 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-06 04:26:31 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-06 04:26:31 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-06 04:26:31 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-06 04:26:31 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-06 04:26:32 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-06 04:26:32 (4259) [INFO] 
* 2023-12-06 04:26:32 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-06 04:26:32 (4229) [INFO] 
* 2023-12-06 04:27:00 (4242) [INFO] 
* 2023-12-06 04:27:00 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-06 04:27:00 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-06 04:27:01 (4259) [INFO] 
* 2023-12-06 04:27:01 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-06 04:27:01 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-06 04:27:03 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-06 04:27:03 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-06 04:27:03 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-06 04:27:03 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-06 04:27: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-12-06 04:27:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-06 04:27:29 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n0rbaAZ8nB/ea_profile.json
* 2023-12-06 04:27:30 (2293) [INFO] Backed up EA4 profile to /tmp/n0rbaAZ8nB/ea_profile.json
* 2023-12-06 04:27:31 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-06 04:27:31 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-07 04:28:11 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-07 04:28:11 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-07 04:28:11 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-07 04:28:11 (4229) [INFO] 
* 2023-12-07 04:28:11 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-07 04:28:11 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-07 04:28:11 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-07 04:28:11 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-07 04:28:11 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-07 04:28:11 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-07 04:28:11 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-07 04:28:12 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-07 04:28:12 (4259) [INFO] 
* 2023-12-07 04:28:12 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-07 04:28:12 (4229) [INFO] 
* 2023-12-07 04:28:46 (4242) [INFO] 
* 2023-12-07 04:28:46 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-07 04:28:46 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-07 04:28:46 (4259) [INFO] 
* 2023-12-07 04:28:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-07 04:28:46 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-07 04:28:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-07 04:28:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-07 04:28:48 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-07 04:28:48 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-07 04:28: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-07 04:29:17 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-07 04:29:17 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7dMPoslEEL/ea_profile.json
* 2023-12-07 04:29:18 (2293) [INFO] Backed up EA4 profile to /tmp/7dMPoslEEL/ea_profile.json
* 2023-12-07 04:29:19 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-07 04:29:19 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-08 04:28:18 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-08 04:28:18 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-08 04:28:18 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-08 04:28:18 (4229) [INFO] 
* 2023-12-08 04:28:19 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-08 04:28:19 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-08 04:28:19 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-08 04:28:19 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-08 04:28:19 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-08 04:28:19 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-08 04:28:19 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-08 04:28:20 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-08 04:28:20 (4259) [INFO] 
* 2023-12-08 04:28:20 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-08 04:28:20 (4229) [INFO] 
* 2023-12-08 04:28:58 (4242) [INFO] 
* 2023-12-08 04:28:58 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-08 04:28:58 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-08 04:28:58 (4259) [INFO] 
* 2023-12-08 04:28:58 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-08 04:28:58 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-08 04:29:00 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-08 04:29:00 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-08 04:29:00 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-08 04:29:00 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-08 04:29: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-12-08 04:29:25 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-08 04:29:25 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9tLZ3IR6W2/ea_profile.json
* 2023-12-08 04:29:26 (2293) [INFO] Backed up EA4 profile to /tmp/9tLZ3IR6W2/ea_profile.json
* 2023-12-08 04:29:27 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-08 04:29:27 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-09 04:27:30 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-09 04:27:30 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-09 04:27:30 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-09 04:27:30 (4229) [INFO] 
* 2023-12-09 04:27:30 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-09 04:27:30 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-09 04:27:30 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-09 04:27:30 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-09 04:27:30 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-09 04:27:30 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-09 04:27:30 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-09 04:27:31 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-09 04:27:31 (4259) [INFO] 
* 2023-12-09 04:27:31 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-09 04:27:31 (4229) [INFO] 
* 2023-12-09 04:28:09 (4242) [INFO] 
* 2023-12-09 04:28:09 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-09 04:28:09 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-09 04:28:09 (4259) [INFO] 
* 2023-12-09 04:28:09 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-09 04:28:09 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-09 04:28:13 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-09 04:28:13 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-09 04:28:13 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-09 04:28:13 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-09 04:28: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-12-09 04:28:39 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-09 04:28:39 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UHfQvb2cn2/ea_profile.json
* 2023-12-09 04:28:40 (2293) [INFO] Backed up EA4 profile to /tmp/UHfQvb2cn2/ea_profile.json
* 2023-12-09 04:28:41 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-09 04:28:41 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-10 04:27:31 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-10 04:27:31 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-10 04:27:31 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-10 04:27:31 (4229) [INFO] 
* 2023-12-10 04:27:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-10 04:27:31 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-10 04:27:31 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-10 04:27:31 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-10 04:27:31 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-10 04:27:31 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-10 04:27:31 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-10 04:27:32 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-10 04:27:32 (4259) [INFO] 
* 2023-12-10 04:27:32 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-10 04:27:32 (4229) [INFO] 
* 2023-12-10 04:28:11 (4242) [INFO] 
* 2023-12-10 04:28:11 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-10 04:28:11 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-10 04:28:11 (4259) [INFO] 
* 2023-12-10 04:28:11 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-10 04:28:12 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-10 04:28:14 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-10 04:28:14 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-10 04:28:14 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-10 04:28:14 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-10 04:28:14 (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 04:28:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-10 04:28:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OOAcdmxX2l/ea_profile.json
* 2023-12-10 04:28:43 (2293) [INFO] Backed up EA4 profile to /tmp/OOAcdmxX2l/ea_profile.json
* 2023-12-10 04:28:44 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-10 04:28:44 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-11 04:26:35 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-11 04:26:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-11 04:26:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-11 04:26:35 (4229) [INFO] 
* 2023-12-11 04:26:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-11 04:26:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-11 04:26:36 (4242) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-11 04:26:36 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-11 04:26:36 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-11 04:26:36 (4242) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-11 04:26:36 (4242) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-11 04:26:36 (4242) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-11 04:26:36 (4259) [INFO] 
* 2023-12-11 04:26:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-11 04:26:36 (4229) [INFO] 
* 2023-12-11 04:27:12 (4242) [INFO] 
* 2023-12-11 04:27:12 (4242) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-11 04:27:12 (4242) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-11 04:27:12 (4259) [INFO] 
* 2023-12-11 04:27:12 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-11 04:27:12 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-11 04:27:15 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-11 04:27:15 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-11 04:27:15 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-11 04:27:15 (1688) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-11 04:27: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-12-11 04:27:41 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-11 04:27:41 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/L68z52yT4Q/ea_profile.json
* 2023-12-11 04:27:42 (2293) [INFO] Backed up EA4 profile to /tmp/L68z52yT4Q/ea_profile.json
* 2023-12-11 04:27:43 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-11 04:27:43 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-12 04:26:33 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-12 04:26:33 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-12 04:26:33 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-12 04:26:33 (4230) [INFO] 
* 2023-12-12 04:26:34 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-12 04:26:34 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-12 04:26:34 (4243) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-12 04:26:34 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-12 04:26:34 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-12 04:26:34 (4243) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-12 04:26:34 (4243) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-12 04:26:34 (4243) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-12 04:26:34 (4260) [INFO] 
* 2023-12-12 04:26:34 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-12 04:26:34 (4230) [INFO] 
* 2023-12-12 04:27:14 (4243) [INFO] 
* 2023-12-12 04:27:14 (4243) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-12 04:27:14 (4243) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-12 04:27:14 (4260) [INFO] 
* 2023-12-12 04:27:14 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-12 04:27:14 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-12 04:27:17 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-12 04:27:17 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-12 04:27:17 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-12 04:27:17 (1689) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-12 04:27:17 (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 04:27:45 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-12 04:27:45 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2nMPjW2_66/ea_profile.json
* 2023-12-12 04:27:47 (2294) [INFO] Backed up EA4 profile to /tmp/2nMPjW2_66/ea_profile.json
* 2023-12-12 04:27:48 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-12 04:27:48 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-13 04:26:36 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-13 04:26:36 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-13 04:26:36 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-13 04:26:36 (4230) [INFO] 
* 2023-12-13 04:26:36 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-13 04:26:37 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-13 04:26:37 (4243) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-13 04:26:37 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-13 04:26:37 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-13 04:26:37 (4243) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-13 04:26:37 (4243) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-13 04:26:37 (4243) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-13 04:26:37 (4260) [INFO] 
* 2023-12-13 04:26:37 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-13 04:26:37 (4230) [INFO] 
* 2023-12-13 04:27:15 (4243) [INFO] 
* 2023-12-13 04:27:15 (4243) [INFO] kernel.x86_64                     3.10.0-1160.102.1.el7                  updates
* 2023-12-13 04:27:15 (4243) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-13 04:27:15 (4260) [INFO] 
* 2023-12-13 04:27:15 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-13 04:27:15 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-13 04:27:18 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-13 04:27:18 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-13 04:27:18 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-13 04:27:18 (1689) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-13 04:27:18 (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 04:27:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-13 04:27:46 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rKXve2_dkj/ea_profile.json
* 2023-12-13 04:27:47 (2294) [INFO] Backed up EA4 profile to /tmp/rKXve2_dkj/ea_profile.json
* 2023-12-13 04:27:48 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-13 04:27:48 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-14 04:30:22 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-14 04:30:22 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-14 04:30:22 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-14 04:30:22 (4230) [INFO] 
* 2023-12-14 04:30:22 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-14 04:30:23 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-14 04:30:23 (4243) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-14 04:30:23 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-14 04:30:23 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-14 04:30:23 (4243) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-14 04:30:23 (4243) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-14 04:30:23 (4243) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-14 04:30:23 (4260) [INFO] 
* 2023-12-14 04:30:23 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-14 04:30:23 (4230) [INFO] 
* 2023-12-14 04:31:00 (4243) [INFO] 
* 2023-12-14 04:31:00 (4243) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-14 04:31:00 (4243) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-14 04:31:01 (4260) [INFO] 
* 2023-12-14 04:31:01 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-14 04:31:01 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-14 04:31:04 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-14 04:31:04 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-14 04:31:04 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-14 04:31:04 (1689) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-14 04:31: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-14 04:31:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-14 04:31:33 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mpp3oxhgyf/ea_profile.json
* 2023-12-14 04:31:34 (2294) [INFO] Backed up EA4 profile to /tmp/mpp3oxhgyf/ea_profile.json
* 2023-12-14 04:31:35 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-14 04:31:35 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-15 04:27:05 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-15 04:27:05 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-15 04:27:05 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-15 04:27:05 (4230) [INFO] 
* 2023-12-15 04:27:05 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-15 04:27:05 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-15 04:27:05 (4243) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-15 04:27:05 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-15 04:27:05 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-15 04:27:05 (4243) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-15 04:27:05 (4243) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-15 04:27:06 (4243) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-15 04:27:06 (4260) [INFO] 
* 2023-12-15 04:27:06 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-15 04:27:06 (4230) [INFO] 
* 2023-12-15 04:27:47 (4243) [INFO] 
* 2023-12-15 04:27:47 (4243) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-15 04:27:47 (4243) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-15 04:27:47 (4260) [INFO] 
* 2023-12-15 04:27:47 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-15 04:27:47 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-15 04:27:50 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-15 04:27:50 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-15 04:27:50 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-15 04:27:50 (1689) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-15 04:27: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-15 04:28:22 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-15 04:28:22 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Z4Nw0YQMVH/ea_profile.json
* 2023-12-15 04:28:23 (2294) [INFO] Backed up EA4 profile to /tmp/Z4Nw0YQMVH/ea_profile.json
* 2023-12-15 04:28:24 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-15 04:28:24 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-16 04:27:37 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-16 04:27:37 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-16 04:27:37 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-16 04:27:37 (4230) [INFO] 
* 2023-12-16 04:27:37 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-16 04:27:38 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-16 04:27:38 (4243) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-16 04:27:38 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-16 04:27:38 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-16 04:27:38 (4243) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-16 04:27:38 (4243) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-16 04:27:38 (4243) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-16 04:27:38 (4260) [INFO] 
* 2023-12-16 04:27:38 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-16 04:27:38 (4230) [INFO] 
* 2023-12-16 04:28:17 (4243) [INFO] 
* 2023-12-16 04:28:17 (4243) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-16 04:28:17 (4243) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-16 04:28:18 (4260) [INFO] 
* 2023-12-16 04:28:18 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-16 04:28:18 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-16 04:28:20 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-16 04:28:20 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-16 04:28:20 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-16 04:28:20 (1689) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-16 04:28:20 (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 04:28:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-16 04:28:49 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YuTeYdue4f/ea_profile.json
* 2023-12-16 04:28:50 (2294) [INFO] Backed up EA4 profile to /tmp/YuTeYdue4f/ea_profile.json
* 2023-12-16 04:28:51 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-16 04:28:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-17 04:27:37 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-17 04:27:37 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-17 04:27:37 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-17 04:27:37 (4230) [INFO] 
* 2023-12-17 04:27:37 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-17 04:27:38 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-17 04:27:38 (4243) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-17 04:27:38 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-17 04:27:38 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-17 04:27:38 (4243) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-17 04:27:38 (4243) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-17 04:27:38 (4243) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-17 04:27:38 (4260) [INFO] 
* 2023-12-17 04:27:38 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-17 04:27:38 (4230) [INFO] 
* 2023-12-17 04:28:20 (4243) [INFO] 
* 2023-12-17 04:28:20 (4243) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-17 04:28:20 (4243) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-17 04:28:20 (4260) [INFO] 
* 2023-12-17 04:28:20 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-17 04:28:20 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-17 04:28:22 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-17 04:28:22 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-17 04:28:22 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-17 04:28:22 (1689) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-17 04:28: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-12-17 04:28:50 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-17 04:28:50 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hP58ev1vIL/ea_profile.json
* 2023-12-17 04:28:51 (2294) [INFO] Backed up EA4 profile to /tmp/hP58ev1vIL/ea_profile.json
* 2023-12-17 04:28:52 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-17 04:28:52 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-18 04:26:41 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-18 04:26:41 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-18 04:26:41 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-18 04:26:41 (4230) [INFO] 
* 2023-12-18 04:26:42 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-18 04:26:42 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-18 04:26:42 (4243) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-18 04:26:42 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-18 04:26:42 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-18 04:26:42 (4243) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-18 04:26:42 (4243) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-18 04:26:42 (4243) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-18 04:26:42 (4260) [INFO] 
* 2023-12-18 04:26:42 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-18 04:26:42 (4230) [INFO] 
* 2023-12-18 04:27:25 (4243) [INFO] 
* 2023-12-18 04:27:25 (4243) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-18 04:27:25 (4243) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-18 04:27:25 (4260) [INFO] 
* 2023-12-18 04:27:25 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-18 04:27:25 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-18 04:27:28 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-18 04:27:28 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-18 04:27:28 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-18 04:27:28 (1689) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-18 04:27:28 (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 04:27:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-18 04:27:56 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lj7fljq40F/ea_profile.json
* 2023-12-18 04:27:57 (2294) [INFO] Backed up EA4 profile to /tmp/lj7fljq40F/ea_profile.json
* 2023-12-18 04:27:58 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-18 04:27:58 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-19 04:26:34 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-19 04:26:34 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-19 04:26:34 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-19 04:26:34 (4230) [INFO] 
* 2023-12-19 04:26:34 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-19 04:26:35 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-19 04:26:35 (4243) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-19 04:26:35 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-19 04:26:35 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-19 04:26:35 (4243) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-19 04:26:35 (4243) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-19 04:26:35 (4243) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-19 04:26:35 (4260) [INFO] 
* 2023-12-19 04:26:35 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-19 04:26:35 (4230) [INFO] 
* 2023-12-19 04:27:15 (4243) [INFO] 
* 2023-12-19 04:27:15 (4243) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-19 04:27:15 (4243) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-19 04:27:15 (4260) [INFO] 
* 2023-12-19 04:27:15 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-19 04:27:15 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-19 04:27:18 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-19 04:27:18 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-19 04:27:18 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-19 04:27:18 (1689) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-19 04:27:18 (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 04:27:45 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-19 04:27:45 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ePOlbUe6Xm/ea_profile.json
* 2023-12-19 04:27:46 (2294) [INFO] Backed up EA4 profile to /tmp/ePOlbUe6Xm/ea_profile.json
* 2023-12-19 04:27:47 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-19 04:27:47 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-20 04:26:42 (488) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-20 04:26:42 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-20 04:26:42 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-20 04:26:42 (4230) [INFO] 
* 2023-12-20 04:26:43 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-20 04:26:43 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-20 04:26:43 (4243) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-20 04:26:43 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-20 04:26:43 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-20 04:26:43 (4243) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-20 04:26:43 (4243) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-20 04:26:43 (4243) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-20 04:26:43 (4260) [INFO] 
* 2023-12-20 04:26:43 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-20 04:26:43 (4230) [INFO] 
* 2023-12-20 04:27:24 (4243) [INFO] 
* 2023-12-20 04:27:24 (4243) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-20 04:27:24 (4243) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-20 04:27:24 (4260) [INFO] 
* 2023-12-20 04:27:24 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-20 04:27:24 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-20 04:27:27 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-20 04:27:27 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-20 04:27:27 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-20 04:27:27 (1689) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-20 04:27: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-12-20 04:27:53 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-20 04:27:53 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_jtA3zvcwJ/ea_profile.json
* 2023-12-20 04:27:54 (2294) [INFO] Backed up EA4 profile to /tmp/_jtA3zvcwJ/ea_profile.json
* 2023-12-20 04:27:55 (155) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-20 04:27:55 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-21 04:28:05 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-21 04:28:05 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-21 04:28:05 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-21 04:28:05 (4251) [INFO] 
* 2023-12-21 04:28:05 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-21 04:28:05 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-21 04:28:05 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-21 04:28:05 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-21 04:28:05 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-21 04:28:05 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-21 04:28:05 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-21 04:28:06 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-21 04:28:06 (4281) [INFO] 
* 2023-12-21 04:28:06 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-21 04:28:06 (4251) [INFO] 
* 2023-12-21 04:28:43 (4264) [INFO] 
* 2023-12-21 04:28:43 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-21 04:28:43 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-21 04:28:43 (4281) [INFO] 
* 2023-12-21 04:28:43 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-21 04:28:43 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-21 04:28:45 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-21 04:28:45 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-21 04:28:45 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-21 04:28:45 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-21 04:29:13 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-21 04:29:13 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/P7bR4PCMiM/ea_profile.json
* 2023-12-21 04:29:14 (2315) [INFO] Backed up EA4 profile to /tmp/P7bR4PCMiM/ea_profile.json
* 2023-12-21 04:29:15 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-21 04:29:15 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-22 04:26:39 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-22 04:26:39 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-22 04:26:39 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-22 04:26:39 (4251) [INFO] 
* 2023-12-22 04:26:40 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-22 04:26:40 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-22 04:26:40 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-22 04:26:40 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-22 04:26:40 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-22 04:26:40 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-22 04:26:40 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-22 04:26:40 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-22 04:26:40 (4281) [INFO] 
* 2023-12-22 04:26:40 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-22 04:26:40 (4251) [INFO] 
* 2023-12-22 04:27:20 (4264) [INFO] 
* 2023-12-22 04:27:20 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-22 04:27:20 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-22 04:27:21 (4281) [INFO] 
* 2023-12-22 04:27:21 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-22 04:27:21 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-22 04:27:23 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-22 04:27:23 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-22 04:27:23 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-22 04:27:23 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-22 04:27:49 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-22 04:27:49 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RKR9gRE2oP/ea_profile.json
* 2023-12-22 04:27:50 (2315) [INFO] Backed up EA4 profile to /tmp/RKR9gRE2oP/ea_profile.json
* 2023-12-22 04:27:51 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-22 04:27:51 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-23 04:27:33 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-23 04:27:33 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-23 04:27:33 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-23 04:27:33 (4251) [INFO] 
* 2023-12-23 04:27:33 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-23 04:27:33 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-23 04:27:33 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-23 04:27:33 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-23 04:27:33 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-23 04:27:33 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-23 04:27:33 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-23 04:27:34 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-23 04:27:34 (4281) [INFO] 
* 2023-12-23 04:27:34 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-23 04:27:34 (4251) [INFO] 
* 2023-12-23 04:28:14 (4264) [INFO] 
* 2023-12-23 04:28:14 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-23 04:28:14 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-23 04:28:14 (4281) [INFO] 
* 2023-12-23 04:28:14 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-23 04:28:14 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-23 04:28:17 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-23 04:28:17 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-23 04:28:17 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-23 04:28:17 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-23 04:28:43 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-23 04:28:43 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/J5_vOiCcER/ea_profile.json
* 2023-12-23 04:28:44 (2315) [INFO] Backed up EA4 profile to /tmp/J5_vOiCcER/ea_profile.json
* 2023-12-23 04:28:45 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-23 04:28:45 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-24 04:27:33 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-24 04:27:33 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-24 04:27:33 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-24 04:27:33 (4251) [INFO] 
* 2023-12-24 04:27:34 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-24 04:27:34 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-24 04:27:34 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-24 04:27:34 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-24 04:27:34 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-24 04:27:34 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-24 04:27:34 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-24 04:27:35 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-24 04:27:35 (4281) [INFO] 
* 2023-12-24 04:27:35 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-24 04:27:35 (4251) [INFO] 
* 2023-12-24 04:28:17 (4264) [INFO] 
* 2023-12-24 04:28:17 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-24 04:28:17 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-24 04:28:18 (4281) [INFO] 
* 2023-12-24 04:28:18 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-24 04:28:18 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-24 04:28:20 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-24 04:28:20 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-24 04:28:20 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-24 04:28:20 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-24 04:28:46 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-24 04:28:46 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6eoIPi5YbU/ea_profile.json
* 2023-12-24 04:28:47 (2315) [INFO] Backed up EA4 profile to /tmp/6eoIPi5YbU/ea_profile.json
* 2023-12-24 04:28:48 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-24 04:28:48 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-25 04:26:35 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-25 04:26:35 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-25 04:26:35 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-25 04:26:35 (4251) [INFO] 
* 2023-12-25 04:26:35 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-25 04:26:36 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-25 04:26:36 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-25 04:26:36 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-25 04:26:36 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-25 04:26:36 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-25 04:26:36 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-25 04:26:36 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-25 04:26:36 (4281) [INFO] 
* 2023-12-25 04:26:36 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-25 04:26:36 (4251) [INFO] 
* 2023-12-25 04:27:14 (4264) [INFO] 
* 2023-12-25 04:27:14 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-25 04:27:14 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-25 04:27:14 (4281) [INFO] 
* 2023-12-25 04:27:14 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-25 04:27:14 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-25 04:27:18 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-25 04:27:18 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-25 04:27:18 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-25 04:27:18 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-25 04:27:46 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-25 04:27:46 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/s8fcBQesse/ea_profile.json
* 2023-12-25 04:27:47 (2315) [INFO] Backed up EA4 profile to /tmp/s8fcBQesse/ea_profile.json
* 2023-12-25 04:27:48 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-25 04:27:48 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-26 04:26:34 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-26 04:26:34 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-26 04:26:34 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-26 04:26:34 (4251) [INFO] 
* 2023-12-26 04:26:35 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-26 04:26:35 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-26 04:26:35 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-26 04:26:35 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-26 04:26:35 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-26 04:26:35 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-26 04:26:35 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-26 04:26:35 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-26 04:26:35 (4281) [INFO] 
* 2023-12-26 04:26:35 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-26 04:26:35 (4251) [INFO] 
* 2023-12-26 04:27:13 (4264) [INFO] 
* 2023-12-26 04:27:13 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-26 04:27:13 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-26 04:27:13 (4281) [INFO] 
* 2023-12-26 04:27:13 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-26 04:27:13 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-26 04:27:16 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-26 04:27:16 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-26 04:27:16 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-26 04:27:16 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-26 04:27:43 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-26 04:27:43 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ERksax14Li/ea_profile.json
* 2023-12-26 04:27:44 (2315) [INFO] Backed up EA4 profile to /tmp/ERksax14Li/ea_profile.json
* 2023-12-26 04:27:45 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-26 04:27:45 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-27 04:26:32 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-27 04:26:32 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-27 04:26:32 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-27 04:26:32 (4251) [INFO] 
* 2023-12-27 04:26:33 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-27 04:26:33 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-27 04:26:33 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-27 04:26:33 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-27 04:26:33 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-27 04:26:33 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-27 04:26:33 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-27 04:26:33 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-27 04:26:33 (4281) [INFO] 
* 2023-12-27 04:26:33 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-27 04:26:33 (4251) [INFO] 
* 2023-12-27 04:27:10 (4264) [INFO] 
* 2023-12-27 04:27:10 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-27 04:27:10 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-27 04:27:10 (4281) [INFO] 
* 2023-12-27 04:27:10 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-27 04:27:10 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-27 04:27:13 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-27 04:27:13 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-27 04:27:13 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-27 04:27:13 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-27 04:27:41 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-27 04:27:41 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8c27IwnISr/ea_profile.json
* 2023-12-27 04:27:42 (2315) [INFO] Backed up EA4 profile to /tmp/8c27IwnISr/ea_profile.json
* 2023-12-27 04:27:43 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-27 04:27:43 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-28 04:26:30 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-28 04:26:30 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-28 04:26:30 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-28 04:26:30 (4251) [INFO] 
* 2023-12-28 04:26:30 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-28 04:26:31 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-28 04:26:31 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-28 04:26:31 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-28 04:26:31 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-28 04:26:31 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-28 04:26:31 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-28 04:26:33 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-28 04:26:33 (4281) [INFO] 
* 2023-12-28 04:26:33 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-28 04:26:33 (4251) [INFO] 
* 2023-12-28 04:27:12 (4264) [INFO] 
* 2023-12-28 04:27:12 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-28 04:27:12 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-28 04:27:12 (4281) [INFO] 
* 2023-12-28 04:27:12 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-28 04:27:12 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-28 04:27:15 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-28 04:27:15 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-28 04:27:15 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-28 04:27:15 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-28 04:27:43 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-28 04:27:43 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W45H2wzxLa/ea_profile.json
* 2023-12-28 04:27:44 (2315) [INFO] Backed up EA4 profile to /tmp/W45H2wzxLa/ea_profile.json
* 2023-12-28 04:27:45 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-28 04:27:45 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-29 04:26:34 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-29 04:26:34 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-29 04:26:34 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-29 04:26:34 (4251) [INFO] 
* 2023-12-29 04:26:34 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-29 04:26:35 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-29 04:26:35 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-29 04:26:35 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-29 04:26:35 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-29 04:26:35 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-29 04:26:35 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-29 04:26:35 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-29 04:26:35 (4281) [INFO] 
* 2023-12-29 04:26:35 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-29 04:26:35 (4251) [INFO] 
* 2023-12-29 04:27:16 (4264) [INFO] 
* 2023-12-29 04:27:16 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-29 04:27:16 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-29 04:27:16 (4281) [INFO] 
* 2023-12-29 04:27:16 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-29 04:27:16 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-29 04:27:19 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-29 04:27:19 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-29 04:27:19 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-29 04:27:19 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-29 04:27:49 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-29 04:27:49 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rC4rCxxdrF/ea_profile.json
* 2023-12-29 04:27:50 (2315) [INFO] Backed up EA4 profile to /tmp/rC4rCxxdrF/ea_profile.json
* 2023-12-29 04:27:51 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-29 04:27:51 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-30 04:27:29 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-30 04:27:29 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-30 04:27:29 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-30 04:27:29 (4251) [INFO] 
* 2023-12-30 04:27:30 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-30 04:27:30 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-30 04:27:30 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-30 04:27:30 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-30 04:27:30 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-30 04:27:30 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-30 04:27:30 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-30 04:27:30 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-30 04:27:30 (4281) [INFO] 
* 2023-12-30 04:27:30 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-30 04:27:30 (4251) [INFO] 
* 2023-12-30 04:28:08 (4264) [INFO] 
* 2023-12-30 04:28:08 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-30 04:28:08 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-30 04:28:08 (4281) [INFO] 
* 2023-12-30 04:28:08 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-30 04:28:08 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-30 04:28:12 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-30 04:28:12 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-30 04:28:12 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-30 04:28:12 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-30 04:28:38 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-30 04:28:38 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/arRA33bQkO/ea_profile.json
* 2023-12-30 04:28:39 (2315) [INFO] Backed up EA4 profile to /tmp/arRA33bQkO/ea_profile.json
* 2023-12-30 04:28:40 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-30 04:28:40 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-31 04:27:34 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2023-12-31 04:27:34 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-31 04:27:34 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-31 04:27:34 (4251) [INFO] 
* 2023-12-31 04:27:34 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-31 04:27:35 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-12-31 04:27:35 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-31 04:27:35 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-31 04:27:35 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-31 04:27:35 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2023-12-31 04:27:35 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2023-12-31 04:27:36 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2023-12-31 04:27:36 (4281) [INFO] 
* 2023-12-31 04:27:36 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-31 04:27:36 (4251) [INFO] 
* 2023-12-31 04:28:16 (4264) [INFO] 
* 2023-12-31 04:28:16 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2023-12-31 04:28:16 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2023-12-31 04:28:16 (4281) [INFO] 
* 2023-12-31 04:28:16 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-31 04:28:16 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-31 04:28:19 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2023-12-31 04:28:19 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2023-12-31 04:28:19 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2023-12-31 04:28:19 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2023-12-31 04:28:49 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-31 04:28:49 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wE4jeptu4J/ea_profile.json
* 2023-12-31 04:28:50 (2315) [INFO] Backed up EA4 profile to /tmp/wE4jeptu4J/ea_profile.json
* 2023-12-31 04:28:50 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2023-12-31 04:28:50 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-01 04:26:31 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-01 04:26:31 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-01 04:26:31 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-01 04:26:31 (4251) [INFO] 
* 2024-01-01 04:26:31 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-01 04:26:31 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-01 04:26:31 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-01 04:26:31 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-01 04:26:31 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-01 04:26:31 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-01 04:26:31 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-01 04:26:32 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-01 04:26:32 (4281) [INFO] 
* 2024-01-01 04:26:32 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-01 04:26:32 (4251) [INFO] 
* 2024-01-01 04:27:11 (4264) [INFO] 
* 2024-01-01 04:27:11 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-01 04:27:11 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-01 04:27:11 (4281) [INFO] 
* 2024-01-01 04:27:11 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-01 04:27:11 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-01 04:27:15 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-01 04:27:15 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-01 04:27:15 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-01 04:27:15 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-01 04:27:42 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-01 04:27:42 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n23sMkEsqF/ea_profile.json
* 2024-01-01 04:27:43 (2315) [INFO] Backed up EA4 profile to /tmp/n23sMkEsqF/ea_profile.json
* 2024-01-01 04:27:43 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-01 04:27:44 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-02 04:26:32 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-02 04:26:32 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-02 04:26:32 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-02 04:26:32 (4251) [INFO] 
* 2024-01-02 04:26:33 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-02 04:26:33 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-02 04:26:33 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-02 04:26:33 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-02 04:26:33 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-02 04:26:33 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-02 04:26:33 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-02 04:26:33 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-02 04:26:33 (4281) [INFO] 
* 2024-01-02 04:26:33 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-02 04:26:33 (4251) [INFO] 
* 2024-01-02 04:27:12 (4264) [INFO] 
* 2024-01-02 04:27:12 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-02 04:27:12 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-02 04:27:12 (4281) [INFO] 
* 2024-01-02 04:27:12 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-02 04:27:12 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-02 04:27:14 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-02 04:27:14 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-02 04:27:14 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-02 04:27:14 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-02 04:27:43 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-02 04:27:43 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rUwU4Tk84y/ea_profile.json
* 2024-01-02 04:27:44 (2315) [INFO] Backed up EA4 profile to /tmp/rUwU4Tk84y/ea_profile.json
* 2024-01-02 04:27:45 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-02 04:27:45 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-03 04:26:36 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-03 04:26:36 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-03 04:26:36 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-03 04:26:36 (4251) [INFO] 
* 2024-01-03 04:26:36 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-03 04:26:37 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-03 04:26:37 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-03 04:26:37 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-03 04:26:37 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-03 04:26:37 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-03 04:26:37 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-03 04:26:37 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-03 04:26:37 (4281) [INFO] 
* 2024-01-03 04:26:37 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-03 04:26:37 (4251) [INFO] 
* 2024-01-03 04:27:17 (4264) [INFO] 
* 2024-01-03 04:27:17 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-03 04:27:17 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-03 04:27:17 (4281) [INFO] 
* 2024-01-03 04:27:17 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-03 04:27:17 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-03 04:27:20 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-03 04:27:20 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-03 04:27:20 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-03 04:27:20 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-03 04:27:47 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-03 04:27:47 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/So8ow5xlNo/ea_profile.json
* 2024-01-03 04:27:48 (2315) [INFO] Backed up EA4 profile to /tmp/So8ow5xlNo/ea_profile.json
* 2024-01-03 04:27:49 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-03 04:27:49 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-04 04:26:58 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-04 04:26:58 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-04 04:26:58 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-04 04:26:58 (4251) [INFO] 
* 2024-01-04 04:26:58 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-04 04:26:58 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-04 04:26:58 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-04 04:26:58 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-04 04:26:58 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-04 04:26:58 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-04 04:26:58 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-04 04:26:59 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-04 04:26:59 (4281) [INFO] 
* 2024-01-04 04:26:59 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-04 04:26:59 (4251) [INFO] 
* 2024-01-04 04:27:36 (4264) [INFO] 
* 2024-01-04 04:27:36 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-04 04:27:36 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-04 04:27:36 (4281) [INFO] 
* 2024-01-04 04:27:36 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-04 04:27:36 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-04 04:27:38 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-04 04:27:38 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-04 04:27:38 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-04 04:27:38 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-04 04:28:06 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-04 04:28:06 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MkZN8366Yz/ea_profile.json
* 2024-01-04 04:28:07 (2315) [INFO] Backed up EA4 profile to /tmp/MkZN8366Yz/ea_profile.json
* 2024-01-04 04:28:08 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-04 04:28:08 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-05 04:26:34 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-05 04:26:34 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-05 04:26:34 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-05 04:26:34 (4251) [INFO] 
* 2024-01-05 04:26:34 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-05 04:26:34 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-05 04:26:34 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-05 04:26:34 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-05 04:26:34 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-05 04:26:34 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-05 04:26:34 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-05 04:26:35 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-05 04:26:35 (4281) [INFO] 
* 2024-01-05 04:26:35 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-05 04:26:35 (4251) [INFO] 
* 2024-01-05 04:27:17 (4264) [INFO] 
* 2024-01-05 04:27:17 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-05 04:27:17 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-05 04:27:17 (4281) [INFO] 
* 2024-01-05 04:27:17 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-05 04:27:17 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-05 04:27:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-05 04:27:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-05 04:27:21 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-05 04:27:21 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-05 04:27:48 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-05 04:27:48 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/02q1eCtOZy/ea_profile.json
* 2024-01-05 04:27:49 (2315) [INFO] Backed up EA4 profile to /tmp/02q1eCtOZy/ea_profile.json
* 2024-01-05 04:27:50 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-05 04:27:50 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-06 04:27:32 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-06 04:27:32 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-06 04:27:32 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-06 04:27:32 (4251) [INFO] 
* 2024-01-06 04:27:33 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-06 04:27:33 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-06 04:27:33 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-06 04:27:33 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-06 04:27:33 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-06 04:27:33 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-06 04:27:33 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-06 04:27:33 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-06 04:27:34 (4281) [INFO] 
* 2024-01-06 04:27:34 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-06 04:27:34 (4251) [INFO] 
* 2024-01-06 04:28:12 (4264) [INFO] 
* 2024-01-06 04:28:12 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-06 04:28:12 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-06 04:28:13 (4281) [INFO] 
* 2024-01-06 04:28:13 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-06 04:28:13 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-06 04:28:15 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-06 04:28:15 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-06 04:28:15 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-06 04:28:15 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-06 04:28:42 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-06 04:28:42 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3tVsyUGl_L/ea_profile.json
* 2024-01-06 04:28:43 (2315) [INFO] Backed up EA4 profile to /tmp/3tVsyUGl_L/ea_profile.json
* 2024-01-06 04:28:44 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-06 04:28:44 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-07 04:27:28 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-07 04:27:28 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-07 04:27:28 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-07 04:27:28 (4251) [INFO] 
* 2024-01-07 04:27:28 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-07 04:27:29 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-07 04:27:29 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-07 04:27:29 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-07 04:27:29 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-07 04:27:29 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-07 04:27:29 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-07 04:27:29 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-07 04:27:29 (4281) [INFO] 
* 2024-01-07 04:27:29 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-07 04:27:29 (4251) [INFO] 
* 2024-01-07 04:28:08 (4264) [INFO] 
* 2024-01-07 04:28:08 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-07 04:28:08 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-07 04:28:08 (4281) [INFO] 
* 2024-01-07 04:28:08 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-07 04:28:08 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-07 04:28:12 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-07 04:28:12 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-07 04:28:12 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-07 04:28:12 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-07 04:28:37 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-07 04:28:37 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7DPOJWPzlY/ea_profile.json
* 2024-01-07 04:28:39 (2315) [INFO] Backed up EA4 profile to /tmp/7DPOJWPzlY/ea_profile.json
* 2024-01-07 04:28:40 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-07 04:28:40 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-08 04:26:39 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-08 04:26:39 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-08 04:26:39 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-08 04:26:39 (4251) [INFO] 
* 2024-01-08 04:26:40 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-08 04:26:40 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-08 04:26:40 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-08 04:26:40 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-08 04:26:40 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-08 04:26:40 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-08 04:26:40 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-08 04:26:40 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-08 04:26:40 (4281) [INFO] 
* 2024-01-08 04:26:40 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-08 04:26:40 (4251) [INFO] 
* 2024-01-08 04:27:22 (4264) [INFO] 
* 2024-01-08 04:27:22 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-08 04:27:22 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-08 04:27:22 (4281) [INFO] 
* 2024-01-08 04:27:22 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-08 04:27:22 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-08 04:27:25 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-08 04:27:25 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-08 04:27:25 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-08 04:27:25 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-08 04:27:53 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-08 04:27:53 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8wF5g0qsg5/ea_profile.json
* 2024-01-08 04:27:54 (2315) [INFO] Backed up EA4 profile to /tmp/8wF5g0qsg5/ea_profile.json
* 2024-01-08 04:27:55 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-08 04:27:55 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-09 04:26:41 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-09 04:26:41 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-09 04:26:41 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-09 04:26:41 (4251) [INFO] 
* 2024-01-09 04:26:41 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-09 04:26:42 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-09 04:26:42 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-09 04:26:42 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-09 04:26:42 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-09 04:26:42 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-09 04:26:42 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-09 04:26:42 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-09 04:26:42 (4281) [INFO] 
* 2024-01-09 04:26:42 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-09 04:26:42 (4251) [INFO] 
* 2024-01-09 04:27:20 (4264) [INFO] 
* 2024-01-09 04:27:20 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-09 04:27:20 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-09 04:27:21 (4281) [INFO] 
* 2024-01-09 04:27:21 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-09 04:27:21 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-09 04:27:23 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-09 04:27:23 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-09 04:27:23 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-09 04:27:23 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-09 04:27:52 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-09 04:27:52 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hXs9K9BbrG/ea_profile.json
* 2024-01-09 04:27:53 (2315) [INFO] Backed up EA4 profile to /tmp/hXs9K9BbrG/ea_profile.json
* 2024-01-09 04:27:54 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-09 04:27:54 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-10 04:26:41 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-10 04:26:41 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-10 04:26:41 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-10 04:26:41 (4251) [INFO] 
* 2024-01-10 04:26:42 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-10 04:26:42 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-10 04:26:42 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-10 04:26:42 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-10 04:26:42 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-10 04:26:42 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-10 04:26:42 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-10 04:26:42 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-10 04:26:42 (4281) [INFO] 
* 2024-01-10 04:26:42 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-10 04:26:42 (4251) [INFO] 
* 2024-01-10 04:27:27 (4264) [INFO] 
* 2024-01-10 04:27:27 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-10 04:27:27 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-10 04:27:28 (4281) [INFO] 
* 2024-01-10 04:27:28 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-10 04:27:28 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-10 04:27:31 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-10 04:27:31 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-10 04:27:31 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-10 04:27:31 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-10 04:27:59 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-10 04:27:59 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SezWIUchAQ/ea_profile.json
* 2024-01-10 04:28:00 (2315) [INFO] Backed up EA4 profile to /tmp/SezWIUchAQ/ea_profile.json
* 2024-01-10 04:28:01 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-10 04:28:01 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-11 04:27:24 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-11 04:27:24 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-11 04:27:24 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-11 04:27:24 (4251) [INFO] 
* 2024-01-11 04:27:24 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-11 04:27:25 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-11 04:27:25 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-11 04:27:25 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-11 04:27:25 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-11 04:27:25 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-11 04:27:25 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-11 04:27:25 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-11 04:27:25 (4281) [INFO] 
* 2024-01-11 04:27:25 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-11 04:27:25 (4251) [INFO] 
* 2024-01-11 04:28:00 (4264) [INFO] 
* 2024-01-11 04:28:00 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-11 04:28:00 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-11 04:28:01 (4281) [INFO] 
* 2024-01-11 04:28:01 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-11 04:28:01 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-11 04:28:03 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-11 04:28:03 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-11 04:28:03 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-11 04:28:03 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-11 04:28:30 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-11 04:28:30 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vIOUQh_UbB/ea_profile.json
* 2024-01-11 04:28:31 (2315) [INFO] Backed up EA4 profile to /tmp/vIOUQh_UbB/ea_profile.json
* 2024-01-11 04:28:32 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-11 04:28:32 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-12 04:26:34 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-12 04:26:34 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-12 04:26:34 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-12 04:26:34 (4251) [INFO] 
* 2024-01-12 04:26:36 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-12 04:26:37 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-12 04:26:37 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-12 04:26:37 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-12 04:26:37 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-12 04:26:37 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-12 04:26:37 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-12 04:26:37 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-12 04:26:37 (4281) [INFO] 
* 2024-01-12 04:26:37 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-12 04:26:37 (4251) [INFO] 
* 2024-01-12 04:27:16 (4264) [INFO] 
* 2024-01-12 04:27:16 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-12 04:27:16 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-12 04:27:16 (4281) [INFO] 
* 2024-01-12 04:27:16 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-12 04:27:16 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-12 04:27:18 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-12 04:27:18 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-12 04:27:18 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-12 04:27:18 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-12 04:27:46 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-12 04:27:46 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gEHYgZn9z7/ea_profile.json
* 2024-01-12 04:27:47 (2315) [INFO] Backed up EA4 profile to /tmp/gEHYgZn9z7/ea_profile.json
* 2024-01-12 04:27:48 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-12 04:27:48 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-13 04:27:39 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-13 04:27:39 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-13 04:27:39 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-13 04:27:39 (4251) [INFO] 
* 2024-01-13 04:27:39 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-13 04:27:39 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-13 04:27:39 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-13 04:27:39 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-13 04:27:39 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-13 04:27:39 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-13 04:27:39 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-13 04:27:40 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-13 04:27:40 (4281) [INFO] 
* 2024-01-13 04:27:40 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-13 04:27:40 (4251) [INFO] 
* 2024-01-13 04:28:17 (4264) [INFO] 
* 2024-01-13 04:28:17 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-13 04:28:17 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-13 04:28:17 (4281) [INFO] 
* 2024-01-13 04:28:17 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-13 04:28:17 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-13 04:28:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-13 04:28:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-13 04:28:21 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-13 04:28:21 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-13 04:28:48 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-13 04:28:48 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1KRH1a26Gv/ea_profile.json
* 2024-01-13 04:28:49 (2315) [INFO] Backed up EA4 profile to /tmp/1KRH1a26Gv/ea_profile.json
* 2024-01-13 04:28:50 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-13 04:28:50 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-14 04:27:23 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-14 04:27:23 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-14 04:27:23 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-14 04:27:23 (4251) [INFO] 
* 2024-01-14 04:27:24 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-14 04:27:24 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-14 04:27:24 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-14 04:27:24 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-14 04:27:24 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-14 04:27:24 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-14 04:27:24 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-14 04:27:24 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-14 04:27:24 (4281) [INFO] 
* 2024-01-14 04:27:24 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-14 04:27:24 (4251) [INFO] 
* 2024-01-14 04:27:54 (4264) [INFO] 
* 2024-01-14 04:27:54 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-14 04:27:54 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-14 04:27:54 (4281) [INFO] 
* 2024-01-14 04:27:54 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-14 04:27:54 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-14 04:27:57 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-14 04:27:57 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-14 04:27:57 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-14 04:27:57 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-14 04:28:23 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-14 04:28:23 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rUBkiapLgL/ea_profile.json
* 2024-01-14 04:28:24 (2315) [INFO] Backed up EA4 profile to /tmp/rUBkiapLgL/ea_profile.json
* 2024-01-14 04:28:24 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-14 04:28:25 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-15 04:26:32 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-15 04:26:32 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-15 04:26:32 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-15 04:26:32 (4251) [INFO] 
* 2024-01-15 04:26:32 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-15 04:26:33 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-15 04:26:33 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-15 04:26:33 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-15 04:26:33 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-15 04:26:33 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-15 04:26:33 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-15 04:26:33 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-15 04:26:33 (4281) [INFO] 
* 2024-01-15 04:26:33 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-15 04:26:33 (4251) [INFO] 
* 2024-01-15 04:27:11 (4264) [INFO] 
* 2024-01-15 04:27:11 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-15 04:27:11 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-15 04:27:11 (4281) [INFO] 
* 2024-01-15 04:27:11 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-15 04:27:11 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-15 04:27:14 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-15 04:27:14 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-15 04:27:14 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-15 04:27:14 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-15 04:27:41 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-15 04:27:41 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ww886IWs49/ea_profile.json
* 2024-01-15 04:27:42 (2315) [INFO] Backed up EA4 profile to /tmp/ww886IWs49/ea_profile.json
* 2024-01-15 04:27:42 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-15 04:27:43 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-16 04:26:34 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-16 04:26:34 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-16 04:26:34 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-16 04:26:34 (4251) [INFO] 
* 2024-01-16 04:26:35 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-16 04:26:35 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-16 04:26:35 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-16 04:26:35 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-16 04:26:35 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-16 04:26:35 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-16 04:26:35 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-16 04:26:35 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-16 04:26:35 (4281) [INFO] 
* 2024-01-16 04:26:35 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-16 04:26:35 (4251) [INFO] 
* 2024-01-16 04:27:17 (4264) [INFO] 
* 2024-01-16 04:27:17 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-16 04:27:17 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-16 04:27:17 (4281) [INFO] 
* 2024-01-16 04:27:17 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-16 04:27:17 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-16 04:27:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-16 04:27:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-16 04:27:21 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-16 04:27:21 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-16 04:27:48 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-16 04:27:48 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_W8jmFMwst/ea_profile.json
* 2024-01-16 04:27:49 (2315) [INFO] Backed up EA4 profile to /tmp/_W8jmFMwst/ea_profile.json
* 2024-01-16 04:27:50 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-16 04:27:50 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-17 04:27:39 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-17 04:27:39 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-17 04:27:39 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-17 04:27:39 (4251) [INFO] 
* 2024-01-17 04:27:39 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-17 04:27:39 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 2524.
* 2024-01-17 04:27:39 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:39 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:39 (4264) [INFO]     Memory :  28 M RSS (1.2 GB VSZ)
* 2024-01-17 04:27:39 (4264) [INFO]     Started: Wed Jan 17 04:27:35 2024 - 00:04 ago
* 2024-01-17 04:27:39 (4264) [INFO]     State  : Sleeping, pid: 2524
* 2024-01-17 04:27:41 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:41 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:41 (4264) [INFO]     Memory :  28 M RSS (1.2 GB VSZ)
* 2024-01-17 04:27:41 (4264) [INFO]     Started: Wed Jan 17 04:27:35 2024 - 00:06 ago
* 2024-01-17 04:27:41 (4264) [INFO]     State  : Sleeping, pid: 2524
* 2024-01-17 04:27:43 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:43 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:43 (4264) [INFO]     Memory :  94 M RSS (1.3 GB VSZ)
* 2024-01-17 04:27:43 (4264) [INFO]     Started: Wed Jan 17 04:27:35 2024 - 00:08 ago
* 2024-01-17 04:27:43 (4264) [INFO]     State  : Running, pid: 2524
* 2024-01-17 04:27:45 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:45 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:45 (4264) [INFO]     Memory : 137 M RSS (1.3 GB VSZ)
* 2024-01-17 04:27:45 (4264) [INFO]     Started: Wed Jan 17 04:27:35 2024 - 00:10 ago
* 2024-01-17 04:27:45 (4264) [INFO]     State  : Uninterruptible, pid: 2524
* 2024-01-17 04:27:47 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:47 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:47 (4264) [INFO]     Memory : 118 M RSS (1.3 GB VSZ)
* 2024-01-17 04:27:47 (4264) [INFO]     Started: Wed Jan 17 04:27:35 2024 - 00:12 ago
* 2024-01-17 04:27:47 (4264) [INFO]     State  : Sleeping, pid: 2524
* 2024-01-17 04:27:49 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:49 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:49 (4264) [INFO]     Memory : 141 M RSS (1.3 GB VSZ)
* 2024-01-17 04:27:49 (4264) [INFO]     Started: Wed Jan 17 04:27:35 2024 - 00:14 ago
* 2024-01-17 04:27:49 (4264) [INFO]     State  : Running, pid: 2524
* 2024-01-17 04:27:51 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-17 04:27:51 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-17 04:27:51 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-17 04:27:51 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-17 04:27:51 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-17 04:27:51 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-17 04:27:52 (4264) [INFO] Cleaning up list of fastest mirrors
* 2024-01-17 04:27:52 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-17 04:27:52 (4281) [INFO] 
* 2024-01-17 04:27:52 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-17 04:27:52 (4251) [INFO] 
* 2024-01-17 04:27:53 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 5946.
* 2024-01-17 04:27:53 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:53 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:53 (4264) [INFO]     Memory :  27 M RSS (246 MB VSZ)
* 2024-01-17 04:27:53 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:02 ago
* 2024-01-17 04:27:53 (4264) [INFO]     State  : Running, pid: 5946
* 2024-01-17 04:27:55 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:55 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:55 (4264) [INFO]     Memory :  30 M RSS (1.2 GB VSZ)
* 2024-01-17 04:27:55 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:04 ago
* 2024-01-17 04:27:55 (4264) [INFO]     State  : Sleeping, pid: 5946
* 2024-01-17 04:27:57 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:57 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:57 (4264) [INFO]     Memory :  30 M RSS (1.2 GB VSZ)
* 2024-01-17 04:27:57 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:06 ago
* 2024-01-17 04:27:57 (4264) [INFO]     State  : Sleeping, pid: 5946
* 2024-01-17 04:27:59 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:27:59 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:27:59 (4264) [INFO]     Memory :  31 M RSS (1.2 GB VSZ)
* 2024-01-17 04:27:59 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:08 ago
* 2024-01-17 04:27:59 (4264) [INFO]     State  : Sleeping, pid: 5946
* 2024-01-17 04:28:01 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:01 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:01 (4264) [INFO]     Memory :  32 M RSS (1.2 GB VSZ)
* 2024-01-17 04:28:01 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:10 ago
* 2024-01-17 04:28:01 (4264) [INFO]     State  : Sleeping, pid: 5946
* 2024-01-17 04:28:03 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:03 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:03 (4264) [INFO]     Memory :  32 M RSS (1.2 GB VSZ)
* 2024-01-17 04:28:03 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:12 ago
* 2024-01-17 04:28:03 (4264) [INFO]     State  : Sleeping, pid: 5946
* 2024-01-17 04:28:05 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:05 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:05 (4264) [INFO]     Memory :  32 M RSS (1.2 GB VSZ)
* 2024-01-17 04:28:05 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:14 ago
* 2024-01-17 04:28:05 (4264) [INFO]     State  : Sleeping, pid: 5946
* 2024-01-17 04:28:07 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:07 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:07 (4264) [INFO]     Memory :  38 M RSS (1.2 GB VSZ)
* 2024-01-17 04:28:07 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:16 ago
* 2024-01-17 04:28:07 (4264) [INFO]     State  : Running, pid: 5946
* 2024-01-17 04:28:09 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:09 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:09 (4264) [INFO]     Memory :  38 M RSS (1.2 GB VSZ)
* 2024-01-17 04:28:09 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:18 ago
* 2024-01-17 04:28:09 (4264) [INFO]     State  : Running, pid: 5946
* 2024-01-17 04:28:11 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:11 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:11 (4264) [INFO]     Memory :  38 M RSS (1.2 GB VSZ)
* 2024-01-17 04:28:11 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:20 ago
* 2024-01-17 04:28:11 (4264) [INFO]     State  : Running, pid: 5946
* 2024-01-17 04:28:13 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:13 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:13 (4264) [INFO]     Memory :  38 M RSS (1.2 GB VSZ)
* 2024-01-17 04:28:13 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:22 ago
* 2024-01-17 04:28:13 (4264) [INFO]     State  : Running, pid: 5946
* 2024-01-17 04:28:15 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:15 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:15 (4264) [INFO]     Memory :  59 M RSS (1.2 GB VSZ)
* 2024-01-17 04:28:15 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:24 ago
* 2024-01-17 04:28:15 (4264) [INFO]     State  : Running, pid: 5946
* 2024-01-17 04:28:17 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:17 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:17 (4264) [INFO]     Memory : 133 M RSS (1.3 GB VSZ)
* 2024-01-17 04:28:17 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:26 ago
* 2024-01-17 04:28:17 (4264) [INFO]     State  : Running, pid: 5946
* 2024-01-17 04:28:19 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:19 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:19 (4264) [INFO]     Memory : 135 M RSS (1.3 GB VSZ)
* 2024-01-17 04:28:19 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:28 ago
* 2024-01-17 04:28:19 (4264) [INFO]     State  : Uninterruptible, pid: 5946
* 2024-01-17 04:28:21 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 04:28:21 (4264) [INFO]   The other application is: yum
* 2024-01-17 04:28:21 (4264) [INFO]     Memory : 135 M RSS (1.3 GB VSZ)
* 2024-01-17 04:28:21 (4264) [INFO]     Started: Wed Jan 17 04:27:51 2024 - 00:30 ago
* 2024-01-17 04:28:21 (4264) [INFO]     State  : Uninterruptible, pid: 5946
* 2024-01-17 04:28:29 (4264) [INFO] 
* 2024-01-17 04:28:29 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-17 04:28:29 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-17 04:28:29 (4281) [INFO] 
* 2024-01-17 04:28:29 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-17 04:28:29 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-17 04:28:31 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-17 04:28:31 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-17 04:28:31 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-17 04:28:31 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-17 04:28:59 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-17 04:28:59 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/y6AoQ9AN0b/ea_profile.json
* 2024-01-17 04:29:00 (2315) [INFO] Backed up EA4 profile to /tmp/y6AoQ9AN0b/ea_profile.json
* 2024-01-17 04:29:01 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-17 04:29:01 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-18 04:28:17 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-18 04:28:17 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-18 04:28:17 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-18 04:28:17 (4251) [INFO] 
* 2024-01-18 04:28:17 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-18 04:28:17 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-18 04:28:17 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-18 04:28:17 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-18 04:28:17 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-18 04:28:17 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-18 04:28:17 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-18 04:28:17 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-18 04:28:17 (4281) [INFO] 
* 2024-01-18 04:28:17 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-18 04:28:17 (4251) [INFO] 
* 2024-01-18 04:28:45 (4264) [INFO] 
* 2024-01-18 04:28:45 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-18 04:28:45 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-18 04:28:45 (4281) [INFO] 
* 2024-01-18 04:28:45 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-18 04:28:45 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-18 04:28:47 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-18 04:28:47 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-18 04:28:47 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-18 04:28:47 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-18 04:29:14 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-18 04:29:14 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/y_1Bwn2W3C/ea_profile.json
* 2024-01-18 04:29:15 (2315) [INFO] Backed up EA4 profile to /tmp/y_1Bwn2W3C/ea_profile.json
* 2024-01-18 04:29:16 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-18 04:29:16 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-19 04:26:41 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-19 04:26:42 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-19 04:26:42 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-19 04:26:42 (4251) [INFO] 
* 2024-01-19 04:26:43 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-19 04:26:44 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-19 04:26:44 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-19 04:26:44 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-19 04:26:44 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-19 04:26:44 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-19 04:26:44 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-19 04:26:44 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-19 04:26:44 (4281) [INFO] 
* 2024-01-19 04:26:44 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-19 04:26:44 (4251) [INFO] 
* 2024-01-19 04:27:22 (4264) [INFO] 
* 2024-01-19 04:27:22 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-19 04:27:22 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-19 04:27:22 (4281) [INFO] 
* 2024-01-19 04:27:22 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-19 04:27:22 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-19 04:27:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-19 04:27:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-19 04:27:25 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-19 04:27:25 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-19 04:27:52 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-19 04:27:52 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6loAvJZh9c/ea_profile.json
* 2024-01-19 04:27:53 (2315) [INFO] Backed up EA4 profile to /tmp/6loAvJZh9c/ea_profile.json
* 2024-01-19 04:27:53 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-19 04:27:53 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-20 04:27:28 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-20 04:27:28 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-20 04:27:28 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-20 04:27:28 (4251) [INFO] 
* 2024-01-20 04:27:28 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-20 04:27:29 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-20 04:27:29 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-20 04:27:29 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-20 04:27:29 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-20 04:27:29 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-20 04:27:29 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-20 04:27:29 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-20 04:27:29 (4281) [INFO] 
* 2024-01-20 04:27:29 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-20 04:27:29 (4251) [INFO] 
* 2024-01-20 04:28:08 (4264) [INFO] 
* 2024-01-20 04:28:08 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-20 04:28:08 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-20 04:28:08 (4281) [INFO] 
* 2024-01-20 04:28:08 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-20 04:28:08 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-20 04:28:11 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-20 04:28:11 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-20 04:28:11 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-20 04:28:11 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-20 04:28:38 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-20 04:28:38 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dbNAllo5HU/ea_profile.json
* 2024-01-20 04:28:39 (2315) [INFO] Backed up EA4 profile to /tmp/dbNAllo5HU/ea_profile.json
* 2024-01-20 04:28:40 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-20 04:28:40 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-21 04:27:27 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-21 04:27:28 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-21 04:27:28 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-21 04:27:28 (4251) [INFO] 
* 2024-01-21 04:27:28 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-21 04:27:28 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-21 04:27:28 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-21 04:27:28 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-21 04:27:28 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-21 04:27:28 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-21 04:27:28 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-21 04:27:29 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-21 04:27:29 (4281) [INFO] 
* 2024-01-21 04:27:29 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-21 04:27:29 (4251) [INFO] 
* 2024-01-21 04:28:06 (4264) [INFO] 
* 2024-01-21 04:28:06 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-21 04:28:06 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-21 04:28:07 (4281) [INFO] 
* 2024-01-21 04:28:07 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-21 04:28:07 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-21 04:28:10 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-21 04:28:10 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-21 04:28:10 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-21 04:28:10 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-21 04:28:38 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-21 04:28:38 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/C5yqKPSqR8/ea_profile.json
* 2024-01-21 04:28:39 (2315) [INFO] Backed up EA4 profile to /tmp/C5yqKPSqR8/ea_profile.json
* 2024-01-21 04:28:40 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-21 04:28:40 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-22 04:26:40 (496) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-22 04:26:40 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-22 04:26:40 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-22 04:26:40 (4251) [INFO] 
* 2024-01-22 04:26:40 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-22 04:26:40 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-22 04:26:40 (4264) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-22 04:26:40 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-22 04:26:40 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-22 04:26:40 (4264) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-22 04:26:40 (4264) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-22 04:26:41 (4264) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-22 04:26:41 (4281) [INFO] 
* 2024-01-22 04:26:41 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-22 04:26:41 (4251) [INFO] 
* 2024-01-22 04:27:20 (4264) [INFO] 
* 2024-01-22 04:27:20 (4264) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-22 04:27:20 (4264) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-22 04:27:20 (4281) [INFO] 
* 2024-01-22 04:27:20 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-22 04:27:20 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-22 04:27:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-22 04:27:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-22 04:27:24 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-22 04:27:24 (1710) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-22 04:27:51 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-22 04:27:51 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iKp8Hyqs2P/ea_profile.json
* 2024-01-22 04:27:52 (2315) [INFO] Backed up EA4 profile to /tmp/iKp8Hyqs2P/ea_profile.json
* 2024-01-22 04:27:53 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-22 04:27:53 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-23 04:26:35 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-23 04:26:36 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-23 04:26:36 (4318) [INFO] Running: /usr/bin/yum clean all
* 2024-01-23 04:26:36 (4319) [INFO] 
* 2024-01-23 04:26:37 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-23 04:26:37 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-23 04:26:37 (4332) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-23 04:26:37 (4332) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-23 04:26:37 (4332) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-23 04:26:37 (4332) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-23 04:26:37 (4332) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-23 04:26:37 (4332) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-23 04:26:37 (4349) [INFO] 
* 2024-01-23 04:26:37 (4318) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-23 04:26:37 (4319) [INFO] 
* 2024-01-23 04:27:18 (4332) [INFO] 
* 2024-01-23 04:27:18 (4332) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-23 04:27:18 (4332) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-23 04:27:18 (4349) [INFO] 
* 2024-01-23 04:27:18 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-23 04:27:18 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-23 04:27:22 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-23 04:27:22 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-23 04:27:22 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-23 04:27:22 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-23 04:27:48 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-23 04:27:48 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_QgiuWMwrN/ea_profile.json
* 2024-01-23 04:27:49 (2383) [INFO] Backed up EA4 profile to /tmp/_QgiuWMwrN/ea_profile.json
* 2024-01-23 04:27:49 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-01-23 04:27:50 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-23 04:27:50 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-24 04:26:39 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-24 04:26:41 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-24 04:26:41 (4318) [INFO] Running: /usr/bin/yum clean all
* 2024-01-24 04:26:41 (4319) [INFO] 
* 2024-01-24 04:26:41 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-24 04:26:41 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-24 04:26:41 (4332) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-24 04:26:41 (4332) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-24 04:26:41 (4332) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-24 04:26:41 (4332) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-24 04:26:41 (4332) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-24 04:26:42 (4332) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-24 04:26:42 (4349) [INFO] 
* 2024-01-24 04:26:42 (4318) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-24 04:26:42 (4319) [INFO] 
* 2024-01-24 04:27:20 (4332) [INFO] 
* 2024-01-24 04:27:20 (4332) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-24 04:27:20 (4332) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-24 04:27:20 (4349) [INFO] 
* 2024-01-24 04:27:20 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-24 04:27:20 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-24 04:27:23 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-24 04:27:23 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-24 04:27:23 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-24 04:27:23 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-24 04:27:50 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-24 04:27:50 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YyW_69KU6o/ea_profile.json
* 2024-01-24 04:27:51 (2383) [INFO] Backed up EA4 profile to /tmp/YyW_69KU6o/ea_profile.json
* 2024-01-24 04:27:51 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-01-24 04:27:52 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-24 04:27:52 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-25 04:28:26 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-25 04:28:27 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-25 04:28:27 (4318) [INFO] Running: /usr/bin/yum clean all
* 2024-01-25 04:28:27 (4319) [INFO] 
* 2024-01-25 04:28:27 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-25 04:28:27 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-25 04:28:27 (4332) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-25 04:28:27 (4332) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-25 04:28:27 (4332) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-25 04:28:27 (4332) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-25 04:28:27 (4332) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-25 04:28:27 (4332) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-25 04:28:27 (4349) [INFO] 
* 2024-01-25 04:28:27 (4318) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-25 04:28:27 (4319) [INFO] 
* 2024-01-25 04:29:00 (4332) [INFO] 
* 2024-01-25 04:29:00 (4332) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-25 04:29:00 (4332) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-25 04:29:00 (4349) [INFO] 
* 2024-01-25 04:29:00 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-25 04:29:00 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-25 04:29:02 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-25 04:29:02 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-25 04:29:02 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-25 04:29:02 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-25 04:29:28 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-25 04:29:28 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7GHBpQ3abP/ea_profile.json
* 2024-01-25 04:29:29 (2383) [INFO] Backed up EA4 profile to /tmp/7GHBpQ3abP/ea_profile.json
* 2024-01-25 04:29:30 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-01-25 04:29:30 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-25 04:29:30 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-26 04:26:56 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-26 04:26:57 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-26 04:26:57 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-26 04:26:57 (4322) [INFO] 
* 2024-01-26 04:26:58 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-26 04:26:58 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-26 04:26:58 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-26 04:26:58 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-26 04:26:58 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-26 04:26:58 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-26 04:26:58 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-26 04:26:59 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-26 04:26:59 (4352) [INFO] 
* 2024-01-26 04:26:59 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-26 04:26:59 (4322) [INFO] 
* 2024-01-26 04:27:39 (4335) [INFO] 
* 2024-01-26 04:27:39 (4335) [INFO] kernel.x86_64                     3.10.0-1160.105.1.el7                  updates
* 2024-01-26 04:27:39 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-26 04:27:39 (4352) [INFO] 
* 2024-01-26 04:27:39 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-26 04:27:39 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-26 04:27:43 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-26 04:27:43 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-26 04:27:43 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-26 04:27:43 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-26 04:28:10 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-26 04:28:10 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S4Tf00gu8h/ea_profile.json
* 2024-01-26 04:28:11 (2382) [INFO] Backed up EA4 profile to /tmp/S4Tf00gu8h/ea_profile.json
* 2024-01-26 04:28:12 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-01-26 04:28:12 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-26 04:28:12 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-27 04:28:19 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-27 04:28:20 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-27 04:28:20 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-27 04:28:20 (4322) [INFO] 
* 2024-01-27 04:28:21 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-27 04:28:21 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-27 04:28:21 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-27 04:28:21 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-27 04:28:21 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-27 04:28:21 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-27 04:28:21 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-27 04:28:21 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-27 04:28:21 (4352) [INFO] 
* 2024-01-27 04:28:21 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-27 04:28:21 (4322) [INFO] 
* 2024-01-27 04:29:03 (4335) [INFO] 
* 2024-01-27 04:29:03 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-01-27 04:29:03 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-27 04:29:03 (4352) [INFO] 
* 2024-01-27 04:29:03 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-27 04:29:03 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-27 04:29:06 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-27 04:29:06 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-27 04:29:06 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-27 04:29:06 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-27 04:29:35 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-27 04:29:35 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ehqzGgk1Wa/ea_profile.json
* 2024-01-27 04:29:36 (2382) [INFO] Backed up EA4 profile to /tmp/ehqzGgk1Wa/ea_profile.json
* 2024-01-27 04:29:37 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-01-27 04:29:37 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-27 04:29:37 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-28 04:28:34 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-28 04:28:35 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-28 04:28:35 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-28 04:28:35 (4322) [INFO] 
* 2024-01-28 04:28:36 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-28 04:28:36 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-28 04:28:36 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-28 04:28:36 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-28 04:28:36 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-28 04:28:36 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-28 04:28:36 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-28 04:28:36 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-28 04:28:36 (4352) [INFO] 
* 2024-01-28 04:28:36 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-28 04:28:36 (4322) [INFO] 
* 2024-01-28 04:29:16 (4335) [INFO] 
* 2024-01-28 04:29:16 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-01-28 04:29:16 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-28 04:29:16 (4352) [INFO] 
* 2024-01-28 04:29:16 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-28 04:29:16 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-28 04:29:18 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-28 04:29:18 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-28 04:29:18 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-28 04:29:18 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-28 04:29:45 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-28 04:29:45 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jxhCw53x9J/ea_profile.json
* 2024-01-28 04:29:46 (2382) [INFO] Backed up EA4 profile to /tmp/jxhCw53x9J/ea_profile.json
* 2024-01-28 04:29:47 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-01-28 04:29:47 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-28 04:29:47 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-29 04:26:44 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-29 04:26:46 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-29 04:26:46 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-29 04:26:46 (4322) [INFO] 
* 2024-01-29 04:26:46 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-29 04:26:47 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-29 04:26:47 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-29 04:26:47 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-29 04:26:47 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-29 04:26:47 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-29 04:26:47 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-29 04:26:47 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-29 04:26:47 (4352) [INFO] 
* 2024-01-29 04:26:47 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-29 04:26:47 (4322) [INFO] 
* 2024-01-29 04:27:28 (4335) [INFO] 
* 2024-01-29 04:27:28 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-01-29 04:27:28 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-29 04:27:28 (4352) [INFO] 
* 2024-01-29 04:27:28 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-29 04:27:28 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-29 04:27:32 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-29 04:27:32 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-29 04:27:32 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-29 04:27:32 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-29 04:28:00 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-29 04:28:00 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gsKWvQL5FC/ea_profile.json
* 2024-01-29 04:28:02 (2382) [INFO] Backed up EA4 profile to /tmp/gsKWvQL5FC/ea_profile.json
* 2024-01-29 04:28:02 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-01-29 04:28:03 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-29 04:28:03 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-30 04:26:46 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-30 04:26:47 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-30 04:26:47 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-30 04:26:47 (4322) [INFO] 
* 2024-01-30 04:26:48 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-30 04:26:48 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-30 04:26:48 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-30 04:26:48 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-30 04:26:48 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-30 04:26:48 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-30 04:26:48 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-30 04:26:48 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-30 04:26:48 (4352) [INFO] 
* 2024-01-30 04:26:48 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-30 04:26:48 (4322) [INFO] 
* 2024-01-30 04:27:34 (4335) [INFO] 
* 2024-01-30 04:27:34 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-01-30 04:27:34 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-30 04:27:34 (4352) [INFO] 
* 2024-01-30 04:27:34 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-30 04:27:34 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-30 04:27:35 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-30 04:27:35 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-30 04:27:35 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-30 04:27:35 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-30 04:28:03 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-30 04:28:03 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/J52kxmcdJo/ea_profile.json
* 2024-01-30 04:28:04 (2382) [INFO] Backed up EA4 profile to /tmp/J52kxmcdJo/ea_profile.json
* 2024-01-30 04:28:04 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-01-30 04:28:05 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-30 04:28:05 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-31 04:26:47 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-01-31 04:26:48 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-31 04:26:48 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-31 04:26:48 (4322) [INFO] 
* 2024-01-31 04:26:48 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-31 04:26:48 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-01-31 04:26:48 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-31 04:26:48 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-31 04:26:48 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-31 04:26:48 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-01-31 04:26:48 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-01-31 04:26:48 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-01-31 04:26:48 (4352) [INFO] 
* 2024-01-31 04:26:48 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-31 04:26:48 (4322) [INFO] 
* 2024-01-31 04:27:17 (4335) [INFO] 
* 2024-01-31 04:27:17 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-01-31 04:27:17 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-01-31 04:27:17 (4352) [INFO] 
* 2024-01-31 04:27:17 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-31 04:27:17 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-31 04:27:20 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-01-31 04:27:20 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-01-31 04:27:20 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-01-31 04:27:20 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-01-31 04:27:50 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-31 04:27:50 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j_XOKjJlvH/ea_profile.json
* 2024-01-31 04:27:51 (2382) [INFO] Backed up EA4 profile to /tmp/j_XOKjJlvH/ea_profile.json
* 2024-01-31 04:27:51 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-01-31 04:27:52 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-01-31 04:27:52 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-01 04:28:32 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-01 04:28:35 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-01 04:28:35 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-01 04:28:35 (4322) [INFO] 
* 2024-02-01 04:28:35 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-01 04:28:36 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-01 04:28:36 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-01 04:28:36 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-01 04:28:36 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-01 04:28:36 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-01 04:28:36 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-01 04:28:36 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-01 04:28:36 (4352) [INFO] 
* 2024-02-01 04:28:36 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-01 04:28:36 (4322) [INFO] 
* 2024-02-01 04:29:16 (4335) [INFO] 
* 2024-02-01 04:29:16 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-01 04:29:16 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-01 04:29:16 (4352) [INFO] 
* 2024-02-01 04:29:16 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-01 04:29:16 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-01 04:29:18 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-01 04:29:18 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-01 04:29:18 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-01 04:29:18 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-01 04:29:47 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-01 04:29:47 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/D3YFtHPB6G/ea_profile.json
* 2024-02-01 04:29:48 (2382) [INFO] Backed up EA4 profile to /tmp/D3YFtHPB6G/ea_profile.json
* 2024-02-01 04:29:48 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-01 04:29:49 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-01 04:29:49 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-02 04:28:08 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-02 04:28:11 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-02 04:28:11 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-02 04:28:11 (4322) [INFO] 
* 2024-02-02 04:28:12 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-02 04:28:12 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-02 04:28:12 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-02 04:28:12 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-02 04:28:12 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-02 04:28:12 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-02 04:28:12 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-02 04:28:13 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-02 04:28:13 (4352) [INFO] 
* 2024-02-02 04:28:13 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-02 04:28:13 (4322) [INFO] 
* 2024-02-02 04:28:54 (4335) [INFO] 
* 2024-02-02 04:28:54 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-02 04:28:54 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-02 04:28:54 (4352) [INFO] 
* 2024-02-02 04:28:54 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-02 04:28:54 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-02 04:28:56 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-02 04:28:56 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-02 04:28:56 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-02 04:28:56 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-02 04:29:24 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-02 04:29:24 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Pbi7C6YxNz/ea_profile.json
* 2024-02-02 04:29:25 (2382) [INFO] Backed up EA4 profile to /tmp/Pbi7C6YxNz/ea_profile.json
* 2024-02-02 04:29:25 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-02 04:29:25 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-02 04:29:26 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-03 04:27:48 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-03 04:27:51 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-03 04:27:51 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-03 04:27:51 (4322) [INFO] 
* 2024-02-03 04:27:51 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-03 04:27:52 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-03 04:27:52 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-03 04:27:52 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-03 04:27:52 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-03 04:27:52 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-03 04:27:52 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-03 04:27:52 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-03 04:27:52 (4352) [INFO] 
* 2024-02-03 04:27:52 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-03 04:27:52 (4322) [INFO] 
* 2024-02-03 04:28:30 (4335) [INFO] 
* 2024-02-03 04:28:30 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-03 04:28:30 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-03 04:28:30 (4352) [INFO] 
* 2024-02-03 04:28:30 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-03 04:28:30 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-03 04:28:32 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-03 04:28:32 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-03 04:28:32 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-03 04:28:32 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-03 04:29:02 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-03 04:29:02 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pGVaFOhPiz/ea_profile.json
* 2024-02-03 04:29:03 (2382) [INFO] Backed up EA4 profile to /tmp/pGVaFOhPiz/ea_profile.json
* 2024-02-03 04:29:03 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-03 04:29:04 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-03 04:29:04 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-04 04:27:30 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-04 04:27:31 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-04 04:27:31 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-04 04:27:31 (4322) [INFO] 
* 2024-02-04 04:27:31 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-04 04:27:32 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-04 04:27:32 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-04 04:27:32 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-04 04:27:32 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-04 04:27:32 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-04 04:27:32 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-04 04:27:32 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-04 04:27:32 (4352) [INFO] 
* 2024-02-04 04:27:32 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-04 04:27:32 (4322) [INFO] 
* 2024-02-04 04:28:15 (4335) [INFO] 
* 2024-02-04 04:28:15 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-04 04:28:15 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-04 04:28:15 (4352) [INFO] 
* 2024-02-04 04:28:15 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-04 04:28:15 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-04 04:28:18 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-04 04:28:18 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-04 04:28:18 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-04 04:28:18 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-04 04:28:47 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-04 04:28:47 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ipZviPpDZj/ea_profile.json
* 2024-02-04 04:28:48 (2382) [INFO] Backed up EA4 profile to /tmp/ipZviPpDZj/ea_profile.json
* 2024-02-04 04:28:49 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-04 04:28:49 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-04 04:28:49 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-05 04:26:39 (502) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-05 04:26:40 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-05 04:26:40 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-05 04:26:40 (4322) [INFO] 
* 2024-02-05 04:26:40 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-05 04:26:41 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-05 04:26:41 (4335) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-05 04:26:41 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-05 04:26:41 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-05 04:26:41 (4335) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-05 04:26:41 (4335) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-05 04:26:43 (4335) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-05 04:26:43 (4352) [INFO] 
* 2024-02-05 04:26:43 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-05 04:26:43 (4322) [INFO] 
* 2024-02-05 04:27:29 (4335) [INFO] 
* 2024-02-05 04:27:29 (4335) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-05 04:27:29 (4335) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-05 04:27:29 (4352) [INFO] 
* 2024-02-05 04:27:29 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-05 04:27:29 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-05 04:27:32 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-05 04:27:32 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-05 04:27:32 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-05 04:27:32 (1778) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-05 04:27:59 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-05 04:27:59 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YhSg9xh4TT/ea_profile.json
* 2024-02-05 04:28:00 (2382) [INFO] Backed up EA4 profile to /tmp/YhSg9xh4TT/ea_profile.json
* 2024-02-05 04:28:00 (161) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-05 04:28:01 (161) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-05 04:28:01 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-06 04:26:58 (504) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-06 04:26:59 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-06 04:26:59 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-06 04:26:59 (4416) [INFO] 
* 2024-02-06 04:26:59 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-06 04:26:59 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-06 04:26:59 (4429) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-06 04:26:59 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-06 04:26:59 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-06 04:26:59 (4429) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-06 04:26:59 (4429) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-06 04:27:00 (4429) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-06 04:27:00 (4446) [INFO] 
* 2024-02-06 04:27:00 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-06 04:27:00 (4416) [INFO] 
* 2024-02-06 04:27:43 (4429) [INFO] 
* 2024-02-06 04:27:43 (4429) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-06 04:27:43 (4429) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-06 04:27:43 (4446) [INFO] 
* 2024-02-06 04:27:43 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-06 04:27:43 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-06 04:27:46 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-06 04:27:46 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-06 04:27:46 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-06 04:27:46 (1780) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-06 04:28:16 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-06 04:28:16 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7ES_V_pWzn/ea_profile.json
* 2024-02-06 04:28:17 (2436) [INFO] Backed up EA4 profile to /tmp/7ES_V_pWzn/ea_profile.json
* 2024-02-06 04:28:18 (162) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-06 04:28:18 (162) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-06 04:28:18 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-07 04:26:40 (504) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-07 04:26:41 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-07 04:26:41 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-07 04:26:41 (4416) [INFO] 
* 2024-02-07 04:26:44 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-07 04:26:45 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-07 04:26:45 (4429) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-07 04:26:45 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-07 04:26:45 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-07 04:26:45 (4429) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-07 04:26:45 (4429) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-07 04:26:45 (4429) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-07 04:26:45 (4446) [INFO] 
* 2024-02-07 04:26:45 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-07 04:26:45 (4416) [INFO] 
* 2024-02-07 04:27:23 (4429) [INFO] 
* 2024-02-07 04:27:23 (4429) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-07 04:27:23 (4429) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-07 04:27:24 (4446) [INFO] 
* 2024-02-07 04:27:24 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-07 04:27:24 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-07 04:27:27 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-07 04:27:27 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-07 04:27:27 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-07 04:27:27 (1780) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-07 04:27:56 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-07 04:27:56 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FU5WLy41ae/ea_profile.json
* 2024-02-07 04:27:57 (2436) [INFO] Backed up EA4 profile to /tmp/FU5WLy41ae/ea_profile.json
* 2024-02-07 04:27:57 (162) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-07 04:27:58 (162) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-07 04:27:58 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-08 04:28:19 (504) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-08 04:28:21 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-08 04:28:21 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-08 04:28:21 (4416) [INFO] 
* 2024-02-08 04:28:21 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-08 04:28:22 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-08 04:28:22 (4429) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-08 04:28:22 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-08 04:28:22 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-08 04:28:22 (4429) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-08 04:28:22 (4429) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-08 04:28:22 (4429) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-08 04:28:23 (4446) [INFO] 
* 2024-02-08 04:28:23 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-08 04:28:23 (4416) [INFO] 
* 2024-02-08 04:29:01 (4429) [INFO] 
* 2024-02-08 04:29:01 (4429) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-08 04:29:01 (4429) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-08 04:29:01 (4446) [INFO] 
* 2024-02-08 04:29:01 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-08 04:29:01 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-08 04:29:03 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-08 04:29:03 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-08 04:29:03 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-08 04:29:03 (1780) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-08 04:29:32 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-08 04:29:32 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bWQe0TJ9ae/ea_profile.json
* 2024-02-08 04:29:33 (2436) [INFO] Backed up EA4 profile to /tmp/bWQe0TJ9ae/ea_profile.json
* 2024-02-08 04:29:34 (162) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-08 04:29:34 (162) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-08 04:29:34 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-09 04:26:41 (504) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-09 04:26:42 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-09 04:26:42 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-09 04:26:42 (4416) [INFO] 
* 2024-02-09 04:26:45 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-09 04:26:45 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-09 04:26:45 (4429) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-09 04:26:45 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-09 04:26:45 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-09 04:26:45 (4429) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-09 04:26:45 (4429) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-09 04:26:46 (4429) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-09 04:26:46 (4446) [INFO] 
* 2024-02-09 04:26:46 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-09 04:26:46 (4416) [INFO] 
* 2024-02-09 04:27:26 (4429) [INFO] 
* 2024-02-09 04:27:26 (4429) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-09 04:27:26 (4429) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-09 04:27:26 (4446) [INFO] 
* 2024-02-09 04:27:26 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-09 04:27:26 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-09 04:27:28 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-09 04:27:28 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-09 04:27:28 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-09 04:27:28 (1780) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-09 04:27:58 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-09 04:27:58 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zgJhq9u2pV/ea_profile.json
* 2024-02-09 04:28:00 (2436) [INFO] Backed up EA4 profile to /tmp/zgJhq9u2pV/ea_profile.json
* 2024-02-09 04:28:00 (162) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-09 04:28:01 (162) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-09 04:28:01 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-10 04:27:35 (504) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-10 04:27:37 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-10 04:27:37 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-10 04:27:37 (4416) [INFO] 
* 2024-02-10 04:27:37 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-10 04:27:37 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-10 04:27:37 (4429) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-10 04:27:37 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-10 04:27:37 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-10 04:27:37 (4429) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-10 04:27:37 (4429) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-10 04:27:38 (4429) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-10 04:27:38 (4446) [INFO] 
* 2024-02-10 04:27:38 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-10 04:27:38 (4416) [INFO] 
* 2024-02-10 04:28:17 (4429) [INFO] 
* 2024-02-10 04:28:17 (4429) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-10 04:28:17 (4429) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-10 04:28:17 (4446) [INFO] 
* 2024-02-10 04:28:17 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-10 04:28:17 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-10 04:28:21 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-10 04:28:21 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-10 04:28:21 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-10 04:28:21 (1780) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-10 04:28:50 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-10 04:28:50 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EclaGItAv0/ea_profile.json
* 2024-02-10 04:28:51 (2436) [INFO] Backed up EA4 profile to /tmp/EclaGItAv0/ea_profile.json
* 2024-02-10 04:28:51 (162) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-10 04:28:52 (162) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-10 04:28:52 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-11 04:27:39 (504) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-11 04:27:40 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-11 04:27:40 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-11 04:27:40 (4416) [INFO] 
* 2024-02-11 04:27:41 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-11 04:27:41 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-11 04:27:41 (4429) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-11 04:27:41 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-11 04:27:41 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-11 04:27:41 (4429) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-11 04:27:41 (4429) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-11 04:27:42 (4429) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-11 04:27:42 (4446) [INFO] 
* 2024-02-11 04:27:42 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-11 04:27:42 (4416) [INFO] 
* 2024-02-11 04:28:22 (4429) [INFO] 
* 2024-02-11 04:28:22 (4429) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-11 04:28:22 (4429) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-11 04:28:22 (4446) [INFO] 
* 2024-02-11 04:28:22 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-11 04:28:22 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-11 04:28:25 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-11 04:28:25 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-11 04:28:25 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-11 04:28:25 (1780) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-11 04:28:52 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-11 04:28:52 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZsosK1yCkH/ea_profile.json
* 2024-02-11 04:28:53 (2436) [INFO] Backed up EA4 profile to /tmp/ZsosK1yCkH/ea_profile.json
* 2024-02-11 04:28:54 (162) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-11 04:28:54 (162) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-11 04:28:54 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-12 04:26:46 (504) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-12 04:26:49 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-12 04:26:49 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-12 04:26:49 (4416) [INFO] 
* 2024-02-12 04:26:49 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-12 04:26:50 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-12 04:26:50 (4429) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-12 04:26:50 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-12 04:26:50 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-12 04:26:50 (4429) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-12 04:26:50 (4429) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-12 04:26:50 (4429) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-12 04:26:50 (4446) [INFO] 
* 2024-02-12 04:26:50 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-12 04:26:50 (4416) [INFO] 
* 2024-02-12 04:27:34 (4429) [INFO] 
* 2024-02-12 04:27:34 (4429) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-12 04:27:34 (4429) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-12 04:27:34 (4446) [INFO] 
* 2024-02-12 04:27:34 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-12 04:27:34 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-12 04:27:36 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-12 04:27:36 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-12 04:27:36 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-12 04:27:36 (1780) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-12 04:28:04 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-12 04:28:04 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5k0_SsxLkF/ea_profile.json
* 2024-02-12 04:28:05 (2436) [INFO] Backed up EA4 profile to /tmp/5k0_SsxLkF/ea_profile.json
* 2024-02-12 04:28:06 (162) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-12 04:28:06 (162) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-12 04:28:06 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-13 04:27:08 (505) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-13 04:27:09 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-13 04:27:09 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-13 04:27:09 (4463) [INFO] 
* 2024-02-13 04:27:09 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-13 04:27:09 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-13 04:27:09 (4476) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-13 04:27:09 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-13 04:27:09 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-13 04:27:09 (4476) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-13 04:27:09 (4476) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-13 04:27:10 (4476) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-13 04:27:10 (4493) [INFO] 
* 2024-02-13 04:27:10 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-13 04:27:10 (4463) [INFO] 
* 2024-02-13 04:27:50 (4476) [INFO] 
* 2024-02-13 04:27:50 (4476) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-13 04:27:50 (4476) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-13 04:27:50 (4493) [INFO] 
* 2024-02-13 04:27:50 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-13 04:27:50 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-13 04:27:53 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-13 04:27:53 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-13 04:27:53 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-13 04:27:53 (1781) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-13 04:28:21 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-13 04:28:21 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zLLHqdhKnQ/ea_profile.json
* 2024-02-13 04:28:22 (2437) [INFO] Backed up EA4 profile to /tmp/zLLHqdhKnQ/ea_profile.json
* 2024-02-13 04:28:22 (163) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-13 04:28:23 (163) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-13 04:28:23 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-14 04:26:42 (505) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-14 04:26:43 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-14 04:26:43 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-14 04:26:43 (4463) [INFO] 
* 2024-02-14 04:26:43 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-14 04:26:44 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-14 04:26:44 (4476) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-14 04:26:44 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-14 04:26:44 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-14 04:26:44 (4476) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-14 04:26:44 (4476) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-14 04:26:44 (4476) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-14 04:26:44 (4493) [INFO] 
* 2024-02-14 04:26:44 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-14 04:26:44 (4463) [INFO] 
* 2024-02-14 04:27:26 (4476) [INFO] 
* 2024-02-14 04:27:26 (4476) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-14 04:27:26 (4476) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-14 04:27:26 (4493) [INFO] 
* 2024-02-14 04:27:26 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-14 04:27:26 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-14 04:27:29 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-14 04:27:29 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-14 04:27:29 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-14 04:27:29 (1781) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-14 04:27:56 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-14 04:27:56 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2Tp7oLnYQH/ea_profile.json
* 2024-02-14 04:27:57 (2437) [INFO] Backed up EA4 profile to /tmp/2Tp7oLnYQH/ea_profile.json
* 2024-02-14 04:27:58 (163) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-14 04:27:58 (163) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-14 04:27:58 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-15 04:26:48 (505) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-15 04:26:50 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-15 04:26:50 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-15 04:26:50 (4463) [INFO] 
* 2024-02-15 04:26:50 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-15 04:26:50 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-15 04:26:50 (4476) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-15 04:26:50 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-15 04:26:50 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-15 04:26:50 (4476) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-15 04:26:50 (4476) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-15 04:26:51 (4476) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-15 04:26:51 (4493) [INFO] 
* 2024-02-15 04:26:51 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-15 04:26:51 (4463) [INFO] 
* 2024-02-15 04:27:38 (4476) [INFO] 
* 2024-02-15 04:27:38 (4476) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-15 04:27:38 (4476) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-15 04:27:38 (4493) [INFO] 
* 2024-02-15 04:27:38 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-15 04:27:38 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-15 04:27:39 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-15 04:27:39 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-15 04:27:39 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-15 04:27:39 (1781) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-15 04:28:06 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-15 04:28:06 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/62h5EyXF81/ea_profile.json
* 2024-02-15 04:28:07 (2437) [INFO] Backed up EA4 profile to /tmp/62h5EyXF81/ea_profile.json
* 2024-02-15 04:28:07 (163) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-15 04:28:08 (163) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-15 04:28:08 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-16 04:26:39 (505) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-16 04:26:40 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-16 04:26:40 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-16 04:26:40 (4463) [INFO] 
* 2024-02-16 04:26:41 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-16 04:26:41 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-16 04:26:41 (4476) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-16 04:26:41 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-16 04:26:41 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-16 04:26:41 (4476) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-16 04:26:41 (4476) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-16 04:26:42 (4476) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-16 04:26:42 (4493) [INFO] 
* 2024-02-16 04:26:42 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-16 04:26:42 (4463) [INFO] 
* 2024-02-16 04:27:20 (4476) [INFO] 
* 2024-02-16 04:27:20 (4476) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-16 04:27:20 (4476) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-16 04:27:20 (4493) [INFO] 
* 2024-02-16 04:27:20 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-16 04:27:20 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-16 04:27:23 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-16 04:27:23 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-16 04:27:23 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-16 04:27:23 (1781) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-16 04:27:50 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-16 04:27:50 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KqN1LMPo0W/ea_profile.json
* 2024-02-16 04:27:51 (2437) [INFO] Backed up EA4 profile to /tmp/KqN1LMPo0W/ea_profile.json
* 2024-02-16 04:27:52 (163) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-16 04:27:52 (163) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-16 04:27:52 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-17 04:28:33 (505) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-17 04:28:34 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-17 04:28:34 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-17 04:28:34 (4463) [INFO] 
* 2024-02-17 04:28:35 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-17 04:28:35 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-17 04:28:35 (4476) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-17 04:28:35 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-17 04:28:35 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-17 04:28:35 (4476) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-17 04:28:35 (4476) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-17 04:28:35 (4476) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-17 04:28:35 (4493) [INFO] 
* 2024-02-17 04:28:35 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-17 04:28:35 (4463) [INFO] 
* 2024-02-17 04:29:17 (4476) [INFO] 
* 2024-02-17 04:29:17 (4476) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-17 04:29:17 (4476) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-17 04:29:17 (4493) [INFO] 
* 2024-02-17 04:29:17 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-17 04:29:17 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-17 04:29:20 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-17 04:29:20 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-17 04:29:20 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-17 04:29:20 (1781) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-17 04:29:46 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-17 04:29:46 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4uZWpXhz2p/ea_profile.json
* 2024-02-17 04:29:47 (2437) [INFO] Backed up EA4 profile to /tmp/4uZWpXhz2p/ea_profile.json
* 2024-02-17 04:29:47 (163) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-17 04:29:48 (163) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-17 04:29:48 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-18 04:27:37 (505) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-18 04:27:38 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-18 04:27:38 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-18 04:27:38 (4463) [INFO] 
* 2024-02-18 04:27:39 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-18 04:27:39 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-18 04:27:39 (4476) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-18 04:27:39 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-18 04:27:39 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-18 04:27:39 (4476) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-18 04:27:39 (4476) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-18 04:27:40 (4476) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-18 04:27:40 (4493) [INFO] 
* 2024-02-18 04:27:40 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-18 04:27:40 (4463) [INFO] 
* 2024-02-18 04:28:20 (4476) [INFO] 
* 2024-02-18 04:28:20 (4476) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-18 04:28:20 (4476) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-18 04:28:21 (4493) [INFO] 
* 2024-02-18 04:28:21 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-18 04:28:21 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-18 04:28:25 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-18 04:28:25 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-18 04:28:25 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-18 04:28:25 (1781) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-18 04:28:51 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-18 04:28:51 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fV3czJ6TVR/ea_profile.json
* 2024-02-18 04:28:52 (2437) [INFO] Backed up EA4 profile to /tmp/fV3czJ6TVR/ea_profile.json
* 2024-02-18 04:28:52 (163) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-18 04:28:53 (163) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-18 04:28:53 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-19 04:27:17 (505) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-19 04:27:20 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-19 04:27:20 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-19 04:27:20 (4463) [INFO] 
* 2024-02-19 04:27:20 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-19 04:27:20 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-19 04:27:20 (4476) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-19 04:27:20 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-19 04:27:20 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-19 04:27:20 (4476) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-19 04:27:20 (4476) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-19 04:27:21 (4476) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-19 04:27:21 (4493) [INFO] 
* 2024-02-19 04:27:21 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-19 04:27:21 (4463) [INFO] 
* 2024-02-19 04:28:02 (4476) [INFO] 
* 2024-02-19 04:28:02 (4476) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-19 04:28:02 (4476) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-19 04:28:02 (4493) [INFO] 
* 2024-02-19 04:28:02 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-19 04:28:02 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-19 04:28:04 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-19 04:28:04 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-19 04:28:04 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-19 04:28:04 (1781) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-19 04:28:30 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-19 04:28:30 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I98hFaoaK3/ea_profile.json
* 2024-02-19 04:28:31 (2437) [INFO] Backed up EA4 profile to /tmp/I98hFaoaK3/ea_profile.json
* 2024-02-19 04:28:31 (163) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-19 04:28:32 (163) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-19 04:28:32 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-20 04:27:09 (505) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-20 04:27:13 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-20 04:27:13 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-20 04:27:13 (4463) [INFO] 
* 2024-02-20 04:27:14 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-20 04:27:14 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-20 04:27:14 (4476) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-20 04:27:14 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-20 04:27:14 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-20 04:27:14 (4476) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-20 04:27:14 (4476) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-20 04:27:15 (4476) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-20 04:27:15 (4493) [INFO] 
* 2024-02-20 04:27:15 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-20 04:27:15 (4463) [INFO] 
* 2024-02-20 04:27:51 (4476) [INFO] 
* 2024-02-20 04:27:51 (4476) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-20 04:27:51 (4476) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-20 04:27:51 (4493) [INFO] 
* 2024-02-20 04:27:51 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-20 04:27:51 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-20 04:27:54 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'letsencrypt-cpanel' from /etc/yum.repos.d/letsencrypt.repo
* 2024-02-20 04:27:54 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-20 04:27:54 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-20 04:27:54 (1781) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-20 04:28:20 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-20 04:28:20 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cqnNXG5J6l/ea_profile.json
* 2024-02-20 04:28:21 (2437) [INFO] Backed up EA4 profile to /tmp/cqnNXG5J6l/ea_profile.json
* 2024-02-20 04:28:21 (163) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-20 04:28:21 (163) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-20 04:28:22 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-21 04:26:36 (514) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-21 04:26:37 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-21 04:26:37 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-21 04:26:37 (4911) [INFO] 
* 2024-02-21 04:26:38 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-21 04:26:38 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-21 04:26:38 (4924) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-21 04:26:38 (4924) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-21 04:26:38 (4924) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-21 04:26:38 (4924) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-21 04:26:38 (4924) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-21 04:26:38 (4924) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-21 04:26:38 (4941) [INFO] 
* 2024-02-21 04:26:38 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-21 04:26:38 (4911) [INFO] 
* 2024-02-21 04:27:07 (4924) [INFO] 
* 2024-02-21 04:27:07 (4924) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-21 04:27:07 (4924) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-21 04:27:07 (4941) [INFO] 
* 2024-02-21 04:27:07 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-21 04:27:07 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-21 04:27:09 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-21 04:27:09 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-21 04:27:09 (1718) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-21 04:27:36 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-21 04:27:36 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5fZwRPajtq/ea_profile.json
* 2024-02-21 04:27:37 (2386) [INFO] Backed up EA4 profile to /tmp/5fZwRPajtq/ea_profile.json
* 2024-02-21 04:27:37 (170) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-21 04:27:38 (170) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-21 04:27:38 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-22 04:27:28 (514) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-22 04:27:30 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-22 04:27:30 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-22 04:27:30 (4911) [INFO] 
* 2024-02-22 04:27:30 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-22 04:27:30 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-22 04:27:30 (4924) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-22 04:27:30 (4924) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-22 04:27:30 (4924) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-22 04:27:30 (4924) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-22 04:27:30 (4924) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-22 04:27:31 (4924) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-22 04:27:31 (4941) [INFO] 
* 2024-02-22 04:27:31 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-22 04:27:31 (4911) [INFO] 
* 2024-02-22 04:28:09 (4924) [INFO] 
* 2024-02-22 04:28:09 (4924) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-22 04:28:09 (4924) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-22 04:28:10 (4941) [INFO] 
* 2024-02-22 04:28:10 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-22 04:28:10 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-22 04:28:12 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-22 04:28:12 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-22 04:28:12 (1718) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-22 04:28:39 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-22 04:28:39 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/A6qXaYRTFm/ea_profile.json
* 2024-02-22 04:28:40 (2386) [INFO] Backed up EA4 profile to /tmp/A6qXaYRTFm/ea_profile.json
* 2024-02-22 04:28:40 (170) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-22 04:28:41 (170) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-22 04:28:41 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-23 04:27:03 (514) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-23 04:27:07 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-23 04:27:07 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-23 04:27:07 (4911) [INFO] 
* 2024-02-23 04:27:07 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-23 04:27:07 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-23 04:27:07 (4924) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-23 04:27:07 (4924) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-23 04:27:07 (4924) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-23 04:27:07 (4924) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-23 04:27:07 (4924) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-23 04:27:07 (4924) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-23 04:27:07 (4941) [INFO] 
* 2024-02-23 04:27:07 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-23 04:27:07 (4911) [INFO] 
* 2024-02-23 04:27:51 (4924) [INFO] 
* 2024-02-23 04:27:51 (4924) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-23 04:27:51 (4924) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-23 04:27:52 (4941) [INFO] 
* 2024-02-23 04:27:52 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-23 04:27:52 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-23 04:27:54 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-23 04:27:54 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-23 04:27:54 (1718) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-23 04:28:26 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-23 04:28:26 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7Uiy52laBr/ea_profile.json
* 2024-02-23 04:28:27 (2386) [INFO] Backed up EA4 profile to /tmp/7Uiy52laBr/ea_profile.json
* 2024-02-23 04:28:27 (170) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-23 04:28:28 (170) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-23 04:28:28 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-24 04:27:43 (514) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-24 04:27:44 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-24 04:27:44 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-24 04:27:44 (4911) [INFO] 
* 2024-02-24 04:27:45 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-24 04:27:45 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-24 04:27:45 (4924) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-24 04:27:45 (4924) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-24 04:27:45 (4924) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-24 04:27:45 (4924) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-24 04:27:45 (4924) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-24 04:27:45 (4924) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-24 04:27:45 (4941) [INFO] 
* 2024-02-24 04:27:45 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-24 04:27:45 (4911) [INFO] 
* 2024-02-24 04:28:25 (4924) [INFO] 
* 2024-02-24 04:28:25 (4924) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-24 04:28:25 (4924) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-24 04:28:25 (4941) [INFO] 
* 2024-02-24 04:28:25 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-24 04:28:25 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-24 04:28:28 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-24 04:28:28 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-24 04:28:28 (1718) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-24 04:28:54 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-24 04:28:54 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EpEm1neWGC/ea_profile.json
* 2024-02-24 04:28:56 (2386) [INFO] Backed up EA4 profile to /tmp/EpEm1neWGC/ea_profile.json
* 2024-02-24 04:28:56 (170) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-24 04:28:56 (170) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-24 04:28:56 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-25 04:27:34 (514) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-25 04:27:36 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-25 04:27:36 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-25 04:27:36 (4911) [INFO] 
* 2024-02-25 04:27:36 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-25 04:27:36 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-25 04:27:36 (4924) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-25 04:27:36 (4924) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-25 04:27:36 (4924) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-25 04:27:36 (4924) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-25 04:27:36 (4924) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-25 04:27:37 (4924) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-25 04:27:37 (4941) [INFO] 
* 2024-02-25 04:27:37 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-25 04:27:37 (4911) [INFO] 
* 2024-02-25 04:28:22 (4924) [INFO] 
* 2024-02-25 04:28:22 (4924) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-25 04:28:22 (4924) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-25 04:28:22 (4941) [INFO] 
* 2024-02-25 04:28:22 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-25 04:28:22 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-25 04:28:25 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-25 04:28:25 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-25 04:28:25 (1718) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-25 04:28:51 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-25 04:28:51 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_HcErfZmAj/ea_profile.json
* 2024-02-25 04:28:52 (2386) [INFO] Backed up EA4 profile to /tmp/_HcErfZmAj/ea_profile.json
* 2024-02-25 04:28:52 (170) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-25 04:28:53 (170) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-25 04:28:53 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-26 04:26:34 (514) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-26 04:26:35 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-26 04:26:35 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-26 04:26:35 (4911) [INFO] 
* 2024-02-26 04:26:36 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-26 04:26:36 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-26 04:26:36 (4924) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-26 04:26:36 (4924) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-26 04:26:36 (4924) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-26 04:26:36 (4924) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-26 04:26:36 (4924) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-26 04:26:36 (4924) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-26 04:26:36 (4941) [INFO] 
* 2024-02-26 04:26:36 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-26 04:26:36 (4911) [INFO] 
* 2024-02-26 04:27:15 (4924) [INFO] 
* 2024-02-26 04:27:15 (4924) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-26 04:27:15 (4924) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-26 04:27:16 (4941) [INFO] 
* 2024-02-26 04:27:16 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-26 04:27:16 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-26 04:27:19 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-26 04:27:19 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-26 04:27:19 (1718) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-26 04:27:49 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-26 04:27:49 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OwtHADLeZw/ea_profile.json
* 2024-02-26 04:27:50 (2386) [INFO] Backed up EA4 profile to /tmp/OwtHADLeZw/ea_profile.json
* 2024-02-26 04:27:50 (170) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-26 04:27:51 (170) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-26 04:27:51 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-27 04:26:44 (514) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-27 04:26:46 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-27 04:26:46 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-27 04:26:46 (4911) [INFO] 
* 2024-02-27 04:26:46 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-27 04:26:46 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-27 04:26:46 (4924) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-27 04:26:46 (4924) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-27 04:26:46 (4924) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-27 04:26:46 (4924) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-27 04:26:46 (4924) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-27 04:26:47 (4924) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-27 04:26:47 (4941) [INFO] 
* 2024-02-27 04:26:47 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-27 04:26:47 (4911) [INFO] 
* 2024-02-27 04:27:31 (4924) [INFO] 
* 2024-02-27 04:27:31 (4924) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-27 04:27:31 (4924) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-27 04:27:32 (4941) [INFO] 
* 2024-02-27 04:27:32 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-27 04:27:32 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-27 04:27:35 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-27 04:27:35 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-27 04:27:35 (1718) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-27 04:28:02 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-27 04:28:02 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mDt1guX4Vn/ea_profile.json
* 2024-02-27 04:28:03 (2386) [INFO] Backed up EA4 profile to /tmp/mDt1guX4Vn/ea_profile.json
* 2024-02-27 04:28:03 (170) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-27 04:28:04 (170) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-27 04:28:04 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-28 04:26:39 (569) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-28 04:26:40 (1828) [INFO] Checking if your system is up to date: 
* 2024-02-28 04:26:40 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-02-28 04:26:40 (5105) [INFO] 
* 2024-02-28 04:26:40 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-28 04:26:40 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-28 04:26:40 (5118) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-28 04:26:40 (5118) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-28 04:26:40 (5118) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-28 04:26:40 (5118) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-28 04:26:40 (5118) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-28 04:26:41 (5118) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-28 04:26:41 (5135) [INFO] 
* 2024-02-28 04:26:41 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-28 04:26:41 (5105) [INFO] 
* 2024-02-28 04:27:19 (5118) [INFO] 
* 2024-02-28 04:27:19 (5118) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-28 04:27:19 (5118) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-28 04:27:19 (5135) [INFO] 
* 2024-02-28 04:27:19 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-28 04:27:19 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-28 04:27:23 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-28 04:27:23 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-28 04:27:23 (1764) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-28 04:27:49 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-28 04:27:49 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w8mCx6znME/ea_profile.json
* 2024-02-28 04:27:51 (2488) [INFO] Backed up EA4 profile to /tmp/w8mCx6znME/ea_profile.json
* 2024-02-28 04:27:51 (173) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-28 04:27:51 (173) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-28 04:27:52 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-29 04:26:43 (569) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-02-29 04:26:44 (1828) [INFO] Checking if your system is up to date: 
* 2024-02-29 04:26:44 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-02-29 04:26:44 (5105) [INFO] 
* 2024-02-29 04:26:44 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-29 04:26:47 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-02-29 04:26:47 (5118) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-29 04:26:47 (5118) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-29 04:26:47 (5118) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-29 04:26:47 (5118) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-02-29 04:26:47 (5118) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-02-29 04:26:48 (5118) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-02-29 04:26:48 (5135) [INFO] 
* 2024-02-29 04:26:48 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-29 04:26:48 (5105) [INFO] 
* 2024-02-29 04:27:32 (5118) [INFO] 
* 2024-02-29 04:27:32 (5118) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-02-29 04:27:32 (5118) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-02-29 04:27:32 (5135) [INFO] 
* 2024-02-29 04:27:32 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-29 04:27:32 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-29 04:27:35 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-02-29 04:27:35 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-02-29 04:27:35 (1764) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-02-29 04:28:01 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-29 04:28:01 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B1NdoWcz3J/ea_profile.json
* 2024-02-29 04:28:02 (2488) [INFO] Backed up EA4 profile to /tmp/B1NdoWcz3J/ea_profile.json
* 2024-02-29 04:28:03 (173) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-02-29 04:28:03 (173) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-02-29 04:28:03 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-01 04:27:13 (569) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-01 04:27:14 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-01 04:27:14 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-01 04:27:14 (5105) [INFO] 
* 2024-03-01 04:27:14 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-01 04:27:14 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-01 04:27:14 (5118) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-01 04:27:14 (5118) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-01 04:27:14 (5118) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-01 04:27:14 (5118) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-01 04:27:14 (5118) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-01 04:27:14 (5118) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-01 04:27:15 (5135) [INFO] 
* 2024-03-01 04:27:15 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-01 04:27:15 (5105) [INFO] 
* 2024-03-01 04:27:44 (5118) [INFO] 
* 2024-03-01 04:27:44 (5118) [INFO] kernel.x86_64                     3.10.0-1160.108.1.el7                  updates
* 2024-03-01 04:27:44 (5118) [INFO] kmod-libs.x86_64                  20-28.el7                              base   
* 2024-03-01 04:27:44 (5135) [INFO] 
* 2024-03-01 04:27:44 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-01 04:27:44 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-03-01 04:27:48 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-01 04:27:48 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-01 04:27:48 (1764) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-01 04:28:14 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-01 04:28:14 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oynWOxUKqP/ea_profile.json
* 2024-03-01 04:28:15 (2488) [INFO] Backed up EA4 profile to /tmp/oynWOxUKqP/ea_profile.json
* 2024-03-01 04:28:16 (173) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php71
- ea-php71-libc-client
- ea-php71-pear
- ea-php71-php-bcmath
- ea-php71-php-bz2
- ea-php71-php-calendar
- ea-php71-php-cli
- ea-php71-php-common
- ea-php71-php-curl
- ea-php71-php-devel
- ea-php71-php-exif
- ea-php71-php-fileinfo
- ea-php71-php-fpm
- ea-php71-php-ftp
- ea-php71-php-gd
- ea-php71-php-iconv
- ea-php71-php-imap
- ea-php71-php-intl
- ea-php71-php-ldap
- ea-php71-php-litespeed
- ea-php71-php-mbstring
- ea-php71-php-mcrypt
- ea-php71-php-mysqlnd
- ea-php71-php-opcache
- ea-php71-php-pdo
- ea-php71-php-posix
- ea-php71-php-sockets
- ea-php71-php-xml
- ea-php71-php-xmlrpc
- ea-php71-php-zip
- ea-php71-runtime

* 2024-03-01 04:28:16 (173) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-03-01 04:28:16 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-02 04:26:54 (569) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-02 04:26:55 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-02 04:26:55 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-02 04:26:55 (5105) [INFO] 
* 2024-03-02 04:26:55 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-02 04:26:55 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-02 04:26:55 (5118) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-02 04:26:55 (5118) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-02 04:26:55 (5118) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-02 04:26:55 (5118) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-02 04:26:55 (5118) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-02 04:26:56 (5118) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-02 04:26:56 (5135) [INFO] 
* 2024-03-02 04:26:56 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-02 04:26:56 (5105) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-02 04:27:05 (5118) [INFO] Trying other mirror.
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-02 04:27:05 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-02 04:27:05 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-02 04:27:05 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-02 04:27:05 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-02 04:27:05 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-02 04:27:05 (5118) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-02 04:27:05 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-02 04:27:05 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-02 04:27:05 (5118) [INFO]         or
* 2024-03-02 04:27:05 (5118) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-02 04:27:05 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-02 04:27:05 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-02 04:27:05 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-02 04:27:05 (5118) [INFO]         compromise:
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-02 04:27:05 (5118) [INFO] 
* 2024-03-02 04:27:05 (5118) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-02 04:27:05 (5118) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-02 04:27:05 (5135) [INFO] 
* 2024-03-02 04:27:05 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-02 04:27:05 (1849) [INFO] Checking /scripts/sysup
* 2024-03-02 04:27:05 (5104) [INFO] Running: /scripts/sysup
* 2024-03-02 04:27:05 (5105) [INFO] 
* 2024-03-02 04:27:06 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-02 04:27:07 (5118) [INFO]   All Needed Packages are already installed.
* 2024-03-02 04:27:07 (5135) [INFO] 
* 2024-03-02 04:27:11 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-02 04:27:11 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-02 04:27:11 (1764) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-02 04:27:14 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-02 04:27:14 (1688) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-02 04:27:14 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-02 04:27:14 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-02 04:27:14 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gtuhMgYS_G/ea_profile.json
* 2024-03-02 04:27:18 (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/gtuhMgYS_G/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-02 04:27:18 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-03 04:26:48 (569) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-03 04:26:49 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-03 04:26:49 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-03 04:26:49 (5105) [INFO] 
* 2024-03-03 04:26:49 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-03 04:26:50 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-03 04:26:50 (5118) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-03 04:26:50 (5118) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-03 04:26:50 (5118) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-03 04:26:50 (5118) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-03 04:26:50 (5118) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-03 04:26:50 (5118) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-03 04:26:50 (5135) [INFO] 
* 2024-03-03 04:26:50 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-03 04:26:50 (5105) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-03 04:26:58 (5118) [INFO] Trying other mirror.
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-03 04:26:58 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-03 04:26:58 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-03 04:26:58 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-03 04:26:58 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-03 04:26:58 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-03 04:26:58 (5118) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-03 04:26:58 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-03 04:26:58 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-03 04:26:58 (5118) [INFO]         or
* 2024-03-03 04:26:58 (5118) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-03 04:26:58 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-03 04:26:58 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-03 04:26:58 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-03 04:26:58 (5118) [INFO]         compromise:
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-03 04:26:58 (5118) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-03 04:26:58 (5118) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-03 04:26:58 (5135) [INFO] 
* 2024-03-03 04:26:58 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-03 04:26:58 (1849) [INFO] Checking /scripts/sysup
* 2024-03-03 04:26:58 (5104) [INFO] Running: /scripts/sysup
* 2024-03-03 04:26:58 (5105) [INFO] 
* 2024-03-03 04:26:58 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-03 04:27:00 (5118) [INFO]   All Needed Packages are already installed.
* 2024-03-03 04:27:00 (5135) [INFO] 
* 2024-03-03 04:27:03 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-03 04:27:03 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-03 04:27:03 (1764) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-03 04:27:07 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-03 04:27:07 (1688) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-03 04:27:07 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-03 04:27:07 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-03 04:27:07 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KRUOG3LmUi/ea_profile.json
* 2024-03-03 04:27:11 (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/KRUOG3LmUi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-03 04:27:11 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-04 04:25:52 (569) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-04 04:25:53 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-04 04:25:53 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-04 04:25:53 (5105) [INFO] 
* 2024-03-04 04:25:53 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-04 04:25:54 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-04 04:25:54 (5118) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-04 04:25:54 (5118) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-04 04:25:54 (5118) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-04 04:25:54 (5118) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-04 04:25:54 (5118) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-04 04:25:54 (5118) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-04 04:25:54 (5135) [INFO] 
* 2024-03-04 04:25:54 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-04 04:25:54 (5105) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-04 04:26:03 (5118) [INFO] Trying other mirror.
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-04 04:26:03 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-04 04:26:03 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-04 04:26:03 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-04 04:26:03 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-04 04:26:03 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-04 04:26:03 (5118) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-04 04:26:03 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-04 04:26:03 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-04 04:26:03 (5118) [INFO]         or
* 2024-03-04 04:26:03 (5118) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-04 04:26:03 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-04 04:26:03 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-04 04:26:03 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-04 04:26:03 (5118) [INFO]         compromise:
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-04 04:26:03 (5118) [INFO] 
* 2024-03-04 04:26:03 (5118) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-04 04:26:03 (5118) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-04 04:26:04 (5135) [INFO] 
* 2024-03-04 04:26:04 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-04 04:26:04 (1849) [INFO] Checking /scripts/sysup
* 2024-03-04 04:26:04 (5104) [INFO] Running: /scripts/sysup
* 2024-03-04 04:26:04 (5105) [INFO] 
* 2024-03-04 04:26:04 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-04 04:26:05 (5118) [INFO]   All Needed Packages are already installed.
* 2024-03-04 04:26:05 (5135) [INFO] 
* 2024-03-04 04:26:09 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-04 04:26:09 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-04 04:26:09 (1764) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-04 04:26:12 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-04 04:26:12 (1688) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-04 04:26:12 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-04 04:26:12 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-04 04:26:12 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B_6tIh2VmZ/ea_profile.json
* 2024-03-04 04:26: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/B_6tIh2VmZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-04 04:26:16 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-05 04:25:50 (569) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-05 04:25:51 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-05 04:25:51 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-05 04:25:51 (5105) [INFO] 
* 2024-03-05 04:25:51 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-05 04:25:52 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-05 04:25:52 (5118) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-05 04:25:52 (5118) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-05 04:25:52 (5118) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-05 04:25:52 (5118) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-05 04:25:52 (5118) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-05 04:25:52 (5118) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-05 04:25:52 (5135) [INFO] 
* 2024-03-05 04:25:52 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-05 04:25:52 (5105) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-05 04:26:02 (5118) [INFO] Trying other mirror.
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-05 04:26:02 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-05 04:26:02 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-05 04:26:02 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-05 04:26:02 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-05 04:26:02 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-05 04:26:02 (5118) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-05 04:26:02 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-05 04:26:02 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-05 04:26:02 (5118) [INFO]         or
* 2024-03-05 04:26:02 (5118) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-05 04:26:02 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-05 04:26:02 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-05 04:26:02 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-05 04:26:02 (5118) [INFO]         compromise:
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-05 04:26:02 (5118) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-05 04:26:02 (5118) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-05 04:26:02 (5135) [INFO] 
* 2024-03-05 04:26:02 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-05 04:26:02 (1849) [INFO] Checking /scripts/sysup
* 2024-03-05 04:26:02 (5104) [INFO] Running: /scripts/sysup
* 2024-03-05 04:26:02 (5105) [INFO] 
* 2024-03-05 04:26:02 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-05 04:26:04 (5118) [INFO]   All Needed Packages are already installed.
* 2024-03-05 04:26:04 (5135) [INFO] 
* 2024-03-05 04:26:07 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-05 04:26:07 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-05 04:26:07 (1764) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-05 04:26:10 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-05 04:26:10 (1688) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-05 04:26:10 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-05 04:26:11 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-05 04:26:11 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yde58Z93u9/ea_profile.json
* 2024-03-05 04:26: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/yde58Z93u9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-05 04:26:14 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-06 04:25:51 (586) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-06 04:25:52 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-06 04:25:52 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-06 04:25:52 (5196) [INFO] 
* 2024-03-06 04:25:52 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-06 04:25:52 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-06 04:25:52 (5209) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-06 04:25:52 (5209) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-06 04:25:52 (5209) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-06 04:25:52 (5209) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-06 04:25:52 (5209) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-06 04:25:52 (5209) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-06 04:25:52 (5226) [INFO] 
* 2024-03-06 04:25:52 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-06 04:25:52 (5196) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-06 04:26:01 (5209) [INFO] Trying other mirror.
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-06 04:26:01 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-06 04:26:01 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-06 04:26:01 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-06 04:26:01 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-06 04:26:01 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-06 04:26:01 (5209) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-06 04:26:01 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-06 04:26:01 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-06 04:26:01 (5209) [INFO]         or
* 2024-03-06 04:26:01 (5209) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-06 04:26:01 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-06 04:26:01 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-06 04:26:01 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-06 04:26:01 (5209) [INFO]         compromise:
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5209) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-06 04:26:01 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-06 04:26:01 (5209) [INFO] 
* 2024-03-06 04:26:01 (5226) [INFO] 
* 2024-03-06 04:26:01 (1940) [INFO] Checking /scripts/sysup
* 2024-03-06 04:26:01 (5195) [INFO] Running: /scripts/sysup
* 2024-03-06 04:26:01 (5196) [INFO] 
* 2024-03-06 04:26:02 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-06 04:26:03 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-06 04:26:03 (5226) [INFO] 
* 2024-03-06 04:26:06 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-06 04:26:06 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-06 04:26:06 (1818) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-06 04:26:10 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-06 04:26:10 (1701) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-06 04:26:10 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-06 04:26:10 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PZpXByVD9P/ea_profile.json
* 2024-03-06 04:26:15 (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/PZpXByVD9P/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-06 04:26:15 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-07 04:25:47 (586) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-07 04:25:48 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-07 04:25:48 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-07 04:25:48 (5196) [INFO] 
* 2024-03-07 04:25:48 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-07 04:25:48 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-07 04:25:48 (5209) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-07 04:25:48 (5209) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-07 04:25:48 (5209) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-07 04:25:48 (5209) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-07 04:25:48 (5209) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-07 04:25:48 (5209) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-07 04:25:48 (5226) [INFO] 
* 2024-03-07 04:25:48 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-07 04:25:48 (5196) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-07 04:25:57 (5209) [INFO] Trying other mirror.
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-07 04:25:57 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-07 04:25:57 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-07 04:25:57 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-07 04:25:57 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-07 04:25:57 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-07 04:25:57 (5209) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-07 04:25:57 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-07 04:25:57 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-07 04:25:57 (5209) [INFO]         or
* 2024-03-07 04:25:57 (5209) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-07 04:25:57 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-07 04:25:57 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-07 04:25:57 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-07 04:25:57 (5209) [INFO]         compromise:
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-07 04:25:57 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-07 04:25:57 (5209) [INFO] 
* 2024-03-07 04:25:57 (5226) [INFO] 
* 2024-03-07 04:25:57 (1940) [INFO] Checking /scripts/sysup
* 2024-03-07 04:25:57 (5195) [INFO] Running: /scripts/sysup
* 2024-03-07 04:25:57 (5196) [INFO] 
* 2024-03-07 04:25:57 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-07 04:25:59 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-07 04:25:59 (5226) [INFO] 
* 2024-03-07 04:26:02 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-07 04:26:02 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-07 04:26:02 (1818) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-07 04:26:05 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-07 04:26:05 (1701) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-07 04:26:06 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-07 04:26:06 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YBP5YaPaYE/ea_profile.json
* 2024-03-07 04:26:10 (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/YBP5YaPaYE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-07 04:26:10 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-08 04:25:46 (586) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-08 04:25:47 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-08 04:25:47 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-08 04:25:47 (5196) [INFO] 
* 2024-03-08 04:25:47 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-08 04:25:47 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-08 04:25:47 (5209) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-08 04:25:47 (5209) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-08 04:25:47 (5209) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-08 04:25:47 (5209) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-08 04:25:47 (5209) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-08 04:25:48 (5209) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-08 04:25:48 (5226) [INFO] 
* 2024-03-08 04:25:48 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-08 04:25:48 (5196) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Unknown error"
* 2024-03-08 04:25:58 (5209) [INFO] Trying other mirror.
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-08 04:25:58 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-08 04:25:58 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-08 04:25:58 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-08 04:25:58 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-08 04:25:58 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-08 04:25:58 (5209) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-08 04:25:58 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-08 04:25:58 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-08 04:25:58 (5209) [INFO]         or
* 2024-03-08 04:25:58 (5209) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-08 04:25:58 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-08 04:25:58 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-08 04:25:58 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-08 04:25:58 (5209) [INFO]         compromise:
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-08 04:25:58 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Unknown error"
* 2024-03-08 04:25:58 (5209) [INFO] 
* 2024-03-08 04:25:58 (5226) [INFO] 
* 2024-03-08 04:25:58 (1940) [INFO] Checking /scripts/sysup
* 2024-03-08 04:25:58 (5195) [INFO] Running: /scripts/sysup
* 2024-03-08 04:25:58 (5196) [INFO] 
* 2024-03-08 04:25:58 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-08 04:26:00 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-08 04:26:00 (5226) [INFO] 
* 2024-03-08 04:26:04 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-08 04:26:04 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-08 04:26:04 (1818) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-08 04:26:08 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-08 04:26:08 (1701) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-08 04:26:09 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-08 04:26:09 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YnI88AEl4z/ea_profile.json
* 2024-03-08 04:26:13 (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/YnI88AEl4z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-08 04:26:13 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-09 04:26:46 (586) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-09 04:26:47 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-09 04:26:47 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-09 04:26:47 (5196) [INFO] 
* 2024-03-09 04:26:48 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-09 04:26:48 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-09 04:26:48 (5209) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-09 04:26:48 (5209) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-09 04:26:48 (5209) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-09 04:26:48 (5209) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-09 04:26:48 (5209) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-09 04:26:48 (5209) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-09 04:26:48 (5226) [INFO] 
* 2024-03-09 04:26:48 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-09 04:26:48 (5196) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-09 04:26:57 (5209) [INFO] Trying other mirror.
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-09 04:26:57 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-09 04:26:57 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-09 04:26:57 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-09 04:26:57 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-09 04:26:57 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-09 04:26:57 (5209) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-09 04:26:57 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-09 04:26:57 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-09 04:26:57 (5209) [INFO]         or
* 2024-03-09 04:26:57 (5209) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-09 04:26:57 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-09 04:26:57 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-09 04:26:57 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-09 04:26:57 (5209) [INFO]         compromise:
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-09 04:26:57 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-09 04:26:57 (5209) [INFO] 
* 2024-03-09 04:26:57 (5226) [INFO] 
* 2024-03-09 04:26:57 (1940) [INFO] Checking /scripts/sysup
* 2024-03-09 04:26:57 (5195) [INFO] Running: /scripts/sysup
* 2024-03-09 04:26:57 (5196) [INFO] 
* 2024-03-09 04:26:57 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-09 04:26:59 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-09 04:26:59 (5226) [INFO] 
* 2024-03-09 04:27:03 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-09 04:27:03 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-09 04:27:03 (1818) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-09 04:27:06 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-09 04:27:06 (1701) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-09 04:27:06 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-09 04:27:06 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/voTL8ASMPV/ea_profile.json
* 2024-03-09 04:27:10 (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/voTL8ASMPV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-09 04:27:10 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-10 04:26:46 (586) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-10 04:26:47 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-10 04:26:47 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-10 04:26:47 (5196) [INFO] 
* 2024-03-10 04:26:47 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-10 04:26:47 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-10 04:26:47 (5209) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-10 04:26:47 (5209) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-10 04:26:47 (5209) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-10 04:26:47 (5209) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-10 04:26:47 (5209) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-10 04:26:47 (5209) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-10 04:26:47 (5226) [INFO] 
* 2024-03-10 04:26:47 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-10 04:26:47 (5196) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-10 04:26:54 (5209) [INFO] Trying other mirror.
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-10 04:26:54 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-10 04:26:54 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-10 04:26:54 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-10 04:26:54 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-10 04:26:54 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-10 04:26:54 (5209) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-10 04:26:54 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-10 04:26:54 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-10 04:26:54 (5209) [INFO]         or
* 2024-03-10 04:26:54 (5209) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-10 04:26:54 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-10 04:26:54 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-10 04:26:54 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-10 04:26:54 (5209) [INFO]         compromise:
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-10 04:26:54 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-10 04:26:54 (5209) [INFO] 
* 2024-03-10 04:26:54 (5226) [INFO] 
* 2024-03-10 04:26:54 (1940) [INFO] Checking /scripts/sysup
* 2024-03-10 04:26:54 (5195) [INFO] Running: /scripts/sysup
* 2024-03-10 04:26:54 (5196) [INFO] 
* 2024-03-10 04:26:54 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-10 04:26:55 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-10 04:26:55 (5226) [INFO] 
* 2024-03-10 04:26:58 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-10 04:26:58 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-10 04:26:58 (1818) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-10 04:27:01 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-10 04:27:01 (1701) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-10 04:27:02 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-10 04:27:02 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OJg903Xayj/ea_profile.json
* 2024-03-10 04:27:05 (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/OJg903Xayj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-10 04:27:05 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-11 04:25:47 (586) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-11 04:25:48 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-11 04:25:48 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-11 04:25:48 (5196) [INFO] 
* 2024-03-11 04:25:49 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-11 04:25:49 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-11 04:25:49 (5209) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-11 04:25:49 (5209) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-11 04:25:49 (5209) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-11 04:25:49 (5209) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-11 04:25:49 (5209) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-11 04:25:49 (5209) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-11 04:25:49 (5226) [INFO] 
* 2024-03-11 04:25:49 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-11 04:25:49 (5196) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-11 04:25:57 (5209) [INFO] Trying other mirror.
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-11 04:25:57 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-11 04:25:57 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-11 04:25:57 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-11 04:25:57 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-11 04:25:57 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-11 04:25:57 (5209) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-11 04:25:57 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-11 04:25:57 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-11 04:25:57 (5209) [INFO]         or
* 2024-03-11 04:25:57 (5209) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-11 04:25:57 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-11 04:25:57 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-11 04:25:57 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-11 04:25:57 (5209) [INFO]         compromise:
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5209) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-11 04:25:57 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-11 04:25:57 (5209) [INFO] 
* 2024-03-11 04:25:57 (5226) [INFO] 
* 2024-03-11 04:25:57 (1940) [INFO] Checking /scripts/sysup
* 2024-03-11 04:25:57 (5195) [INFO] Running: /scripts/sysup
* 2024-03-11 04:25:57 (5196) [INFO] 
* 2024-03-11 04:25:58 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-11 04:25:59 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-11 04:25:59 (5226) [INFO] 
* 2024-03-11 04:26:03 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-11 04:26:03 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-11 04:26:03 (1818) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-11 04:26:06 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-11 04:26:06 (1701) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-11 04:26:07 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-11 04:26:07 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ftRh_RAO3x/ea_profile.json
* 2024-03-11 04:26:11 (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/ftRh_RAO3x/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-11 04:26:11 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-12 04:25:46 (586) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-12 04:25:46 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-12 04:25:46 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-12 04:25:46 (5196) [INFO] 
* 2024-03-12 04:25:47 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-12 04:25:47 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-12 04:25:47 (5209) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-12 04:25:47 (5209) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-12 04:25:47 (5209) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-12 04:25:47 (5209) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-12 04:25:47 (5209) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-12 04:25:47 (5209) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-12 04:25:47 (5226) [INFO] 
* 2024-03-12 04:25:47 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-12 04:25:47 (5196) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-12 04:25:57 (5209) [INFO] Trying other mirror.
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-12 04:25:57 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-12 04:25:57 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-12 04:25:57 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-12 04:25:57 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-12 04:25:57 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-12 04:25:57 (5209) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-12 04:25:57 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-12 04:25:57 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-12 04:25:57 (5209) [INFO]         or
* 2024-03-12 04:25:57 (5209) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-12 04:25:57 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-12 04:25:57 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-12 04:25:57 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-12 04:25:57 (5209) [INFO]         compromise:
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-12 04:25:57 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-12 04:25:57 (5209) [INFO] 
* 2024-03-12 04:25:57 (5226) [INFO] 
* 2024-03-12 04:25:57 (1940) [INFO] Checking /scripts/sysup
* 2024-03-12 04:25:57 (5195) [INFO] Running: /scripts/sysup
* 2024-03-12 04:25:57 (5196) [INFO] 
* 2024-03-12 04:25:57 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-12 04:25:58 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-12 04:25:58 (5226) [INFO] 
* 2024-03-12 04:26:02 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-12 04:26:02 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-12 04:26:02 (1818) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-12 04:26:05 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-12 04:26:05 (1701) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-12 04:26:06 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-12 04:26:06 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4NLyRfqkhP/ea_profile.json
* 2024-03-12 04:26:09 (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/4NLyRfqkhP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-12 04:26:09 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-13 04:25:53 (586) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-13 04:25:54 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-13 04:25:54 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-13 04:25:54 (5196) [INFO] 
* 2024-03-13 04:25:54 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-13 04:25:54 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-03-13 04:25:54 (5209) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-03-13 04:25:54 (5209) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-03-13 04:25:54 (5209) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-03-13 04:25:54 (5209) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-03-13 04:25:54 (5209) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-03-13 04:25:54 (5209) [INFO] Other repos take up 4.0 M of disk space (use --verbose for details)
* 2024-03-13 04:25:54 (5226) [INFO] 
* 2024-03-13 04:25:54 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-13 04:25:54 (5196) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-13 04:26:01 (5209) [INFO] Trying other mirror.
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO]  One of the configured repositories failed (Let's Encrypt for cPanel),
* 2024-03-13 04:26:01 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-13 04:26:01 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-13 04:26:01 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-13 04:26:01 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-13 04:26:01 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-13 04:26:01 (5209) [INFO]             yum --disablerepo=letsencrypt-cpanel ...
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-13 04:26:01 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-13 04:26:01 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO]             yum-config-manager --disable letsencrypt-cpanel
* 2024-03-13 04:26:01 (5209) [INFO]         or
* 2024-03-13 04:26:01 (5209) [INFO]             subscription-manager repos --disable=letsencrypt-cpanel
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-13 04:26:01 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-13 04:26:01 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-13 04:26:01 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-13 04:26:01 (5209) [INFO]         compromise:
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO]             yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5209) [INFO] failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
* 2024-03-13 04:26:01 (5209) [INFO] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-13 04:26:01 (5209) [INFO] 
* 2024-03-13 04:26:01 (5226) [INFO] 
* 2024-03-13 04:26:01 (1940) [INFO] Checking /scripts/sysup
* 2024-03-13 04:26:01 (5195) [INFO] Running: /scripts/sysup
* 2024-03-13 04:26:01 (5196) [INFO] 
* 2024-03-13 04:26:02 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-13 04:26:03 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-13 04:26:03 (5226) [INFO] 
* 2024-03-13 04:26:06 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-13 04:26:06 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-13 04:26:06 (1818) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-13 04:26:09 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-13 04:26:09 (1701) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-13 04:26:10 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-13 04:26:10 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/S6IEsuvB4X/ea_profile.json
* 2024-03-13 04:26:13 (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/S6IEsuvB4X/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-13 04:26:13 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-14 04:25:50 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-14 04:25:54 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-14 04:25:54 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-14 04:25:54 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-14 04:26:02 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-14 04:26:02 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-14 04:26:02 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-14 04:26:02 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gb_xg_sVEQ/ea_profile.json
* 2024-03-14 04:26:06 (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/gb_xg_sVEQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-14 04:26:06 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-15 04:25:45 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-15 04:25:48 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-15 04:25:48 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-15 04:25:48 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-15 04:25:55 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-15 04:25:55 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-15 04:25:55 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-15 04:25:55 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zw5ES0A99O/ea_profile.json
* 2024-03-15 04:25:59 (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/zw5ES0A99O/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-15 04:25:59 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-16 04:26:47 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-16 04:26:50 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-16 04:26:50 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-16 04:26:50 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-16 04:26:59 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-16 04:26:59 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-16 04:26:59 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-16 04:26:59 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rpSs1x3cfF/ea_profile.json
* 2024-03-16 04:27:03 (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/rpSs1x3cfF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-16 04:27:03 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-17 04:26:45 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-17 04:26:50 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-17 04:26:50 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-17 04:26:50 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-17 04:26:57 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-17 04:26:57 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-17 04:26:57 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-17 04:26:57 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jR8swRsmWw/ea_profile.json
* 2024-03-17 04:27:01 (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/jR8swRsmWw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-17 04:27:01 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-18 04:25:48 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-18 04:25:52 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-18 04:25:52 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-18 04:25:52 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-18 04:26:01 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-18 04:26:01 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-18 04:26:01 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-18 04:26:01 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8HRWk9TVPx/ea_profile.json
* 2024-03-18 04:26:04 (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/8HRWk9TVPx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-18 04:26:04 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-19 04:25:47 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-19 04:25:50 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-19 04:25:50 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-19 04:25:50 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-19 04:25:57 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-19 04:25:57 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-19 04:25:58 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-19 04:25:58 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oSSOtWmpUz/ea_profile.json
* 2024-03-19 04:26:01 (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/oSSOtWmpUz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-19 04:26:01 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-20 04:25:55 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-20 04:25:58 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-20 04:25:58 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-20 04:25:58 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-20 04:26:10 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-20 04:26:10 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-20 04:26:10 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-20 04:26:10 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6oYvUcEw1Z/ea_profile.json
* 2024-03-20 04:26: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/6oYvUcEw1Z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-20 04:26:20 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-21 04:25:48 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-21 04:25:52 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-21 04:25:52 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-21 04:25:52 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-21 04:25:58 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-21 04:25:58 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-21 04:25:59 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-21 04:25:59 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dc2TY6AiJC/ea_profile.json
* 2024-03-21 04:26:03 (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/dc2TY6AiJC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-21 04:26:03 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-22 04:25:53 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-22 04:25:57 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-22 04:25:57 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-22 04:25:57 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-22 04:26:05 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-22 04:26:05 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-22 04:26:05 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-22 04:26:05 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lfbazvN_eo/ea_profile.json
* 2024-03-22 04:26:10 (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/lfbazvN_eo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-22 04:26:10 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-23 04:26:40 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-23 04:26:43 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-23 04:26:43 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-23 04:26:43 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-23 04:26:51 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-23 04:26:51 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-23 04:26:51 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-23 04:26:51 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PoAuaOMSqs/ea_profile.json
* 2024-03-23 04:26:55 (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/PoAuaOMSqs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-23 04:26:55 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-24 04:26:45 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-24 04:26:49 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-24 04:26:49 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-24 04:26:49 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-24 04:26:56 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-24 04:26:56 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-24 04:26:57 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-24 04:26:57 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/A5MEUAQAiD/ea_profile.json
* 2024-03-24 04:27:00 (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/A5MEUAQAiD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-24 04:27:00 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-25 04:25:45 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-25 04:25:49 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-25 04:25:49 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-25 04:25:49 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-25 04:25:55 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-25 04:25:55 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-25 04:25:55 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-25 04:25:55 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sptfzaPilX/ea_profile.json
* 2024-03-25 04:25: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/sptfzaPilX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-25 04:25:58 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-26 04:25:52 (588) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-26 04:25:55 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-26 04:25:55 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-26 04:25:55 (1834) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-26 04:26:04 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-26 04:26:04 (1717) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-26 04:26:04 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-26 04:26:04 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xNiUhK6vXO/ea_profile.json
* 2024-03-26 04:26:07 (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/xNiUhK6vXO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-26 04:26:07 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-27 04:25:47 (592) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-27 04:25:51 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-27 04:25:51 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-27 04:25:51 (1872) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-27 04:25:58 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-27 04:25:58 (1755) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-27 04:25:59 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-27 04:25:59 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/X_nagkoi0d/ea_profile.json
* 2024-03-27 04:26:03 (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/X_nagkoi0d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-27 04:26:03 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-28 04:25:50 (592) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-28 04:25:53 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-28 04:25:53 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-28 04:25:53 (1872) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-28 04:25:59 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-28 04:25:59 (1755) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-28 04:26:00 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-28 04:26:00 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AezHAFtTSL/ea_profile.json
* 2024-03-28 04:26:03 (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/AezHAFtTSL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-28 04:26:03 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-29 04:25:50 (592) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-29 04:25:54 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-29 04:25:54 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-29 04:25:54 (1872) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-29 04:26:02 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-29 04:26:02 (1755) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-29 04:26:02 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-29 04:26:02 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aBwTH7ICqD/ea_profile.json
* 2024-03-29 04:26:06 (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/aBwTH7ICqD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-29 04:26:06 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-30 04:26:45 (592) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-30 04:26:49 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-30 04:26:49 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-30 04:26:49 (1872) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-30 04:26:57 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-30 04:26:57 (1755) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-30 04:26:57 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-30 04:26:57 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LjKSjR74SX/ea_profile.json
* 2024-03-30 04:27:01 (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/LjKSjR74SX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-30 04:27:01 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-31 04:26:42 (592) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-03-31 04:26:45 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-03-31 04:26:45 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-03-31 04:26:45 (1872) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-03-31 04:26:53 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-31 04:26:53 (1755) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-03-31 04:26:53 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-31 04:26:53 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hvUeMtnDCL/ea_profile.json
* 2024-03-31 04:26:57 (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/hvUeMtnDCL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-31 04:26:57 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-01 04:25:44 (592) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-01 04:25:48 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-01 04:25:48 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-01 04:25:48 (1872) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-01 04:25:54 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-01 04:25:54 (1755) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-01 04:25:55 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-01 04:25:55 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GdDrh4wAvC/ea_profile.json
* 2024-04-01 04:25:58 (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/GdDrh4wAvC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-04-01 04:25:58 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-02 04:25:50 (592) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-02 04:25:53 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-02 04:25:53 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-02 04:25:53 (1872) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-02 04:26:00 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-02 04:26:00 (1755) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-02 04:26:01 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-02 04:26:01 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/W4wa3gIsOX/ea_profile.json
* 2024-04-02 04:26:04 (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/W4wa3gIsOX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-04-02 04:26:04 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-03 04:25:50 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-03 04:25:53 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-03 04:25:53 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-03 04:25:53 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-03 04:26:00 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-03 04:26:00 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-03 04:26:01 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-03 04:26:01 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HEloMizHSm/ea_profile.json
* 2024-04-03 04:26:05 (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/HEloMizHSm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-03 04:26:05 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-04 04:25:54 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-04 04:25:58 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-04 04:25:58 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-04 04:25:58 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-04 04:26:08 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-04 04:26:08 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-04 04:26:09 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-04 04:26:09 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4lxDb_DS4R/ea_profile.json
* 2024-04-04 04:26:12 (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/4lxDb_DS4R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-04 04:26:12 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-05 04:25:49 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-05 04:25:52 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-05 04:25:52 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-05 04:25:52 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-05 04:25:59 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-05 04:25:59 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-05 04:25:59 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-05 04:25:59 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/A2q3x2_D_0/ea_profile.json
* 2024-04-05 04:26:04 (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/A2q3x2_D_0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-05 04:26:04 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-06 04:26:45 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-06 04:26:49 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-06 04:26:49 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-06 04:26:49 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-06 04:26:57 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-06 04:26:57 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-06 04:26:57 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-06 04:26:57 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mmnd3PDmnA/ea_profile.json
* 2024-04-06 04:27:02 (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/mmnd3PDmnA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-06 04:27:02 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-07 04:26:43 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-07 04:26:47 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-07 04:26:47 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-07 04:26:47 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-07 04:26:54 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-07 04:26:54 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-07 04:26:54 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-07 04:26:54 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fWB2ruDZMg/ea_profile.json
* 2024-04-07 04:26: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/fWB2ruDZMg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-07 04:26:58 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-08 04:25:52 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-08 04:25:55 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-08 04:25:55 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-08 04:25:55 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-08 04:26:02 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-08 04:26:02 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-08 04:26:03 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-08 04:26:03 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZVtAKIE78H/ea_profile.json
* 2024-04-08 04:26:06 (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/ZVtAKIE78H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-08 04:26:06 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-09 04:25:47 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-09 04:25:51 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-09 04:25:51 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-09 04:25:51 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-09 04:25:58 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-09 04:25:58 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-09 04:25:59 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-09 04:25:59 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oz_nQah_Lw/ea_profile.json
* 2024-04-09 04:26:03 (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/oz_nQah_Lw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-09 04:26:03 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-10 04:25:50 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-10 04:25:54 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-10 04:25:54 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-10 04:25:54 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-10 04:26:01 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-10 04:26:01 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-10 04:26:01 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-10 04:26:01 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pHFzkEpybM/ea_profile.json
* 2024-04-10 04:26:05 (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/pHFzkEpybM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-10 04:26:05 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-11 04:25:49 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-11 04:25:52 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-11 04:25:52 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-11 04:25:52 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-11 04:26:01 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-11 04:26:01 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-11 04:26:01 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-11 04:26:01 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/g4B_g4u19P/ea_profile.json
* 2024-04-11 04:26:05 (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/g4B_g4u19P/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-11 04:26:05 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-12 04:25:53 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-12 04:25:56 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-12 04:25:56 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-12 04:25:56 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-12 04:26:03 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-12 04:26:03 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-12 04:26:03 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-12 04:26:03 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BFjLzdXcog/ea_profile.json
* 2024-04-12 04:26: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/BFjLzdXcog/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-12 04:26:07 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-13 04:26:51 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-13 04:26:56 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-13 04:26:56 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-13 04:26:56 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-13 04:27:05 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-13 04:27:05 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-13 04:27:05 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-13 04:27:05 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dK0GTtFB0w/ea_profile.json
* 2024-04-13 04:27: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/dK0GTtFB0w/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-13 04:27:08 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-14 04:26:44 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-14 04:26:47 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-14 04:26:47 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-14 04:26:47 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-14 04:26:54 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-14 04:26:54 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-14 04:26:55 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-14 04:26:55 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GngoQ0xbXL/ea_profile.json
* 2024-04-14 04:26: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/GngoQ0xbXL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-14 04:26:58 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-15 04:25:53 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-15 04:25:56 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-15 04:25:56 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-15 04:25:56 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-15 04:26:03 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-15 04:26:03 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-15 04:26:04 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-15 04:26:04 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8EvinrqW99/ea_profile.json
* 2024-04-15 04:26: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/8EvinrqW99/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-15 04:26:08 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-16 04:26:46 (6907) [INFO] Self-update of script version 33 requested.
* 2024-04-16 04:26:46 (6929) [INFO] Script is up to date.
* 2024-04-16 04:26:52 (595) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-16 04:26:59 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-16 04:26:59 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-16 04:26:59 (1877) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-16 04:27:07 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-16 04:27:07 (1760) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-16 04:27:08 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-16 04:27:08 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IdLR5RxgHO/ea_profile.json
* 2024-04-16 04:27:12 (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/IdLR5RxgHO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-16 04:27:12 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-17 04:25:45 (6907) [INFO] Self-update of script version 33 requested.
* 2024-04-17 04:25:45 (6912) [INFO] Newer version of script found. Downloading.
* 2024-04-17 04:25:46 (6921) [INFO] Script update to version 34 successful.
* 2024-04-17 04:25:49 (593) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-17 04:25:52 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-17 04:25:52 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-17 04:25:52 (1894) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-17 04:26:00 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-17 04:26:00 (1777) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-17 04:26:00 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-17 04:26:00 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5FSKO1cozG/ea_profile.json
* 2024-04-17 04:26:05 (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/5FSKO1cozG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-17 04:26:05 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-18 04:25:54 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-18 04:25:54 (7128) [INFO] Script is up to date.
* 2024-04-18 04:25:59 (593) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-18 04:26:03 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-18 04:26:03 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-18 04:26:03 (1894) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-18 04:26:11 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-18 04:26:11 (1777) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-18 04:26:11 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-18 04:26:11 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/D8mdq2hu3A/ea_profile.json
* 2024-04-18 04:26:15 (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/D8mdq2hu3A/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-18 04:26:15 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-19 04:27:54 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-19 04:27:54 (7128) [INFO] Script is up to date.
* 2024-04-19 04:27:59 (593) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-19 04:28:04 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-19 04:28:04 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-19 04:28:04 (1894) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-19 04:28:50 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-19 04:28:50 (1777) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-19 04:28:51 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-19 04:28:51 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/l8StyDUV8B/ea_profile.json
* 2024-04-19 04:29:13 (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/l8StyDUV8B/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-19 04:29:13 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-20 04:27:16 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-20 04:27:16 (7128) [INFO] Script is up to date.
* 2024-04-20 04:27:21 (593) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-20 04:27:26 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-20 04:27:26 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-20 04:27:26 (1894) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-20 04:27:39 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-20 04:27:39 (1777) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-20 04:27:39 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-20 04:27:39 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IrXUK09Jsu/ea_profile.json
* 2024-04-20 04:27:44 (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/IrXUK09Jsu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-20 04:27:44 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-21 04:26:42 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-21 04:26:42 (7128) [INFO] Script is up to date.
* 2024-04-21 04:26:46 (593) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-21 04:26:50 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-21 04:26:50 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-21 04:26:50 (1894) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-21 04:26:59 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-21 04:26:59 (1777) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-21 04:27:00 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-21 04:27:00 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TqQHorqbFl/ea_profile.json
* 2024-04-21 04:27:06 (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/TqQHorqbFl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-21 04:27:06 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-22 04:25:53 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-22 04:25:54 (7128) [INFO] Script is up to date.
* 2024-04-22 04:25:56 (593) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-22 04:25:59 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-22 04:25:59 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-22 04:25:59 (1894) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-22 04:26:07 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-22 04:26:07 (1777) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-22 04:26:07 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-22 04:26:07 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WweypAaZlR/ea_profile.json
* 2024-04-22 04:26:12 (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/WweypAaZlR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-22 04:26:12 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-23 04:25:47 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-23 04:25:47 (7128) [INFO] Script is up to date.
* 2024-04-23 04:25:50 (593) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-23 04:25:53 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-23 04:25:53 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-23 04:25:53 (1894) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-23 04:26:00 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-23 04:26:00 (1777) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-23 04:26:01 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-23 04:26:01 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ex8KOLa1xR/ea_profile.json
* 2024-04-23 04:26: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/Ex8KOLa1xR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-23 04:26:04 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-24 04:26:36 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-24 04:26:36 (7128) [INFO] Script is up to date.
* 2024-04-24 04:26:41 (593) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-24 04:26:46 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-24 04:26:46 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-24 04:26:46 (1894) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-24 04:26:54 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-24 04:26:54 (1777) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-24 04:26:54 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-24 04:26:54 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HyZmtP5nMN/ea_profile.json
* 2024-04-24 04:26: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/HyZmtP5nMN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-24 04:26:58 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-25 04:25:49 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-25 04:25:49 (7128) [INFO] Script is up to date.
* 2024-04-25 04:25:52 (593) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-25 04:25:57 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-25 04:25:57 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-25 04:25:57 (1894) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-25 04:26:06 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-25 04:26:06 (1777) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-25 04:26:07 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-25 04:26:07 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2QpeGt4QFW/ea_profile.json
* 2024-04-25 04:26:10 (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/2QpeGt4QFW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-25 04:26:10 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-26 04:25:44 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-26 04:25:44 (7111) [INFO] Newer version of script found. Downloading.
* 2024-04-26 04:25:45 (7120) [INFO] Script update to version 35 successful.
* 2024-04-26 04:25:46 (596) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-26 04:25:49 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-26 04:25:49 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-26 04:25:49 (1903) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-26 04:25:56 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-26 04:25:56 (1786) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-26 04:25:57 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-26 04:25:57 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Vgk_XFdLm2/ea_profile.json
* 2024-04-26 04:25:59 (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/Vgk_XFdLm2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-26 04:25:59 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-27 04:26:45 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-27 04:26:45 (7138) [INFO] Script is up to date.
* 2024-04-27 04:26:47 (596) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-27 04:26:51 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-27 04:26:51 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-27 04:26:51 (1903) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-27 04:26:59 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-27 04:26:59 (1786) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-27 04:27:00 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-27 04:27:00 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Bhoo0Mtdfm/ea_profile.json
* 2024-04-27 04:27:03 (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/Bhoo0Mtdfm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-27 04:27:03 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-28 04:26:48 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-28 04:26:48 (7138) [INFO] Script is up to date.
* 2024-04-28 04:26:51 (596) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-28 04:26:55 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-28 04:26:55 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-28 04:26:55 (1903) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-28 04:27:03 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-28 04:27:03 (1786) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-28 04:27:03 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-28 04:27:03 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bFkN3f1D6D/ea_profile.json
* 2024-04-28 04:27:07 (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/bFkN3f1D6D/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-28 04:27:07 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-29 04:25:45 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-29 04:25:45 (7138) [INFO] Script is up to date.
* 2024-04-29 04:25:48 (596) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-29 04:25:51 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-29 04:25:51 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-29 04:25:51 (1903) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-29 04:25:58 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-29 04:25:58 (1786) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-29 04:25:58 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-29 04:25:58 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2abZvShQKb/ea_profile.json
* 2024-04-29 04:26:02 (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/2abZvShQKb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-29 04:26:02 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-30 04:25:44 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-30 04:25:44 (7138) [INFO] Script is up to date.
* 2024-04-30 04:25:46 (596) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-04-30 04:25:48 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-04-30 04:25:48 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-04-30 04:25:48 (1903) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-04-30 04:25:55 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-30 04:25:55 (1786) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-04-30 04:25:55 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-30 04:25:55 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XQubDUO9Xa/ea_profile.json
* 2024-04-30 04:25:59 (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/XQubDUO9Xa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-30 04:25:59 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-01 04:25:46 (7116) [INFO] Self-update of script version 35 requested.
* 2024-05-01 04:25:46 (7121) [INFO] Newer version of script found. Downloading.
* 2024-05-01 04:25:47 (7130) [INFO] Script update to version 36 successful.
* 2024-05-01 04:25:49 (597) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-01 04:25:53 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-01 04:25:53 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-01 04:25:53 (1904) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-01 04:26:00 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-01 04:26:00 (1787) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-01 04:26:01 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-01 04:26:01 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iqigbMDT64/ea_profile.json
* 2024-05-01 04:26:04 (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/iqigbMDT64/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-01 04:26:04 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-02 04:25:47 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-02 04:25:47 (7530) [INFO] Script is up to date.
* 2024-05-02 04:25:50 (597) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-02 04:25:53 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-02 04:25:53 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-02 04:25:53 (1904) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-02 04:26:00 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-02 04:26:00 (1787) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-02 04:26:00 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-02 04:26:00 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Rb2NHu0652/ea_profile.json
* 2024-05-02 04:26:03 (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/Rb2NHu0652/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-02 04:26:03 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-03 04:25:45 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-03 04:25:46 (7530) [INFO] Script is up to date.
* 2024-05-03 04:25:48 (597) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-03 04:25:51 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-03 04:25:51 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-03 04:25:51 (1904) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-03 04:26:00 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-03 04:26:00 (1787) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-03 04:26:01 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-03 04:26:01 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3QjzvYJmY8/ea_profile.json
* 2024-05-03 04:26:04 (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/3QjzvYJmY8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-03 04:26:04 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-04 04:26:45 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-04 04:26:45 (7530) [INFO] Script is up to date.
* 2024-05-04 04:26:49 (597) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-04 04:26:53 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-04 04:26:53 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-04 04:26:53 (1904) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-04 04:27:02 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-04 04:27:02 (1787) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Unknown error"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Unknown error"
* 2024-05-04 04:27:02 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-04 04:27:02 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AweHhMAnkr/ea_profile.json
* 2024-05-04 04:27:06 (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/AweHhMAnkr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-04 04:27:06 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-05 04:26:46 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-05 04:26:46 (7530) [INFO] Script is up to date.
* 2024-05-05 04:26:49 (597) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-05 04:26:52 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-05 04:26:52 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-05 04:26:52 (1904) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-05 04:27:00 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-05 04:27:00 (1787) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-05 04:27:01 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-05 04:27:01 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mXXSANR2lH/ea_profile.json
* 2024-05-05 04:27:04 (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/mXXSANR2lH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-05 04:27:04 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-06 04:25:47 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-06 04:25:47 (7530) [INFO] Script is up to date.
* 2024-05-06 04:25:50 (597) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-06 04:25:52 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-06 04:25:52 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-06 04:25:52 (1904) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-06 04:26:01 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-06 04:26:01 (1787) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-06 04:26:01 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-06 04:26:01 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/go9Uwxd2dh/ea_profile.json
* 2024-05-06 04:26:05 (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/go9Uwxd2dh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-06 04:26:05 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-07 04:25:40 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-07 04:25:40 (7513) [INFO] Newer version of script found. Downloading.
* 2024-05-07 04:25:40 (7522) [INFO] Script update to version 37 successful.
* 2024-05-07 04:25:41 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-07 04:25:41 (6322) [INFO] 
* 2024-05-07 04:25:41 (6352) [INFO] 
* 2024-05-07 04:25:42 (600) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-07 04:25:44 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-07 04:25:44 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-07 04:25:44 (1943) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-07 04:25:50 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-07 04:25:50 (1826) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-07 04:25:51 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-07 04:25:51 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pWVvsKHUqz/ea_profile.json
* 2024-05-07 04:25:53 (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/pWVvsKHUqz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-07 04:25:53 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-08 04:25:43 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-08 04:25:43 (7570) [INFO] Script is up to date.
* 2024-05-08 04:25:46 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-08 04:25:46 (6322) [INFO] 
* 2024-05-08 04:25:46 (6352) [INFO] 
* 2024-05-08 04:25:48 (600) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-08 04:25:52 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-08 04:25:52 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-08 04:25:52 (1943) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-08 04:25:58 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-08 04:25:58 (1826) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-08 04:25:59 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-08 04:25:59 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qHC0j0slcp/ea_profile.json
* 2024-05-08 04:26:01 (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/qHC0j0slcp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-08 04:26:01 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-09 04:25:46 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-09 04:25:46 (7570) [INFO] Script is up to date.
* 2024-05-09 04:25:48 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-09 04:25:48 (6322) [INFO] 
* 2024-05-09 04:25:48 (6352) [INFO] 
* 2024-05-09 04:25:48 (600) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-09 04:25:52 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-09 04:25:52 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-09 04:25:52 (1943) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-09 04:25:58 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-09 04:25:58 (1826) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-09 04:25:59 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-09 04:25:59 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cyooaADLqB/ea_profile.json
* 2024-05-09 04:26:02 (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/cyooaADLqB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-09 04:26:02 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-10 04:25:46 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-10 04:25:47 (7570) [INFO] Script is up to date.
* 2024-05-10 04:25:50 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-10 04:25:50 (6322) [INFO] 
* 2024-05-10 04:25:50 (6352) [INFO] 
* 2024-05-10 04:25:51 (600) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-10 04:25:56 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-10 04:25:56 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-10 04:25:56 (1943) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-10 04:26:02 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-10 04:26:02 (1826) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-10 04:26:03 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-10 04:26:03 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZWAwMxK5zt/ea_profile.json
* 2024-05-10 04:26:05 (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/ZWAwMxK5zt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-10 04:26:05 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-11 04:26:45 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-11 04:26:45 (7570) [INFO] Script is up to date.
* 2024-05-11 04:26:47 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-11 04:26:47 (6322) [INFO] 
* 2024-05-11 04:26:47 (6352) [INFO] 
* 2024-05-11 04:26:48 (600) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-11 04:26:51 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-11 04:26:51 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-11 04:26:51 (1943) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-11 04:26:58 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-11 04:26:58 (1826) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-11 04:26:59 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-11 04:26:59 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fJOJ9T7vEN/ea_profile.json
* 2024-05-11 04:27:02 (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/fJOJ9T7vEN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-11 04:27:02 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-12 04:26:41 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-12 04:26:41 (7570) [INFO] Script is up to date.
* 2024-05-12 04:26:44 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-12 04:26:44 (6322) [INFO] 
* 2024-05-12 04:26:44 (6352) [INFO] 
* 2024-05-12 04:26:44 (600) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-12 04:26:48 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-12 04:26:48 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-12 04:26:48 (1943) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-12 04:26:55 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-12 04:26:55 (1826) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-12 04:26:56 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-12 04:26:56 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_m1k78RUIL/ea_profile.json
* 2024-05-12 04:27:00 (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/_m1k78RUIL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-12 04:27:00 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-13 04:25:49 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-13 04:25:49 (7570) [INFO] Script is up to date.
* 2024-05-13 04:25:51 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-13 04:25:51 (6322) [INFO] 
* 2024-05-13 04:25:51 (6352) [INFO] 
* 2024-05-13 04:25:52 (600) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-13 04:25:56 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-13 04:25:56 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-13 04:25:56 (1943) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-13 04:26:04 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-13 04:26:04 (1826) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-13 04:26:04 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-13 04:26:04 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lBfzdo4cxW/ea_profile.json
* 2024-05-13 04:26: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/lBfzdo4cxW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-13 04:26:08 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-14 04:25:45 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-14 04:25:45 (7570) [INFO] Script is up to date.
* 2024-05-14 04:25:46 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-14 04:25:46 (6322) [INFO] 
* 2024-05-14 04:25:46 (6352) [INFO] 
* 2024-05-14 04:25:47 (600) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-14 04:25:50 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-14 04:25:50 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-14 04:25:50 (1943) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-14 04:25:56 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-14 04:25:56 (1826) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-14 04:25:56 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-14 04:25:56 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kBGO8zNAII/ea_profile.json
* 2024-05-14 04:26:00 (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/kBGO8zNAII/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-14 04:26:00 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-15 04:25:43 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-15 04:25:43 (7570) [INFO] Script is up to date.
* 2024-05-15 04:25:46 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-15 04:25:46 (6322) [INFO] 
* 2024-05-15 04:25:46 (6352) [INFO] 
* 2024-05-15 04:25:47 (600) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-15 04:25:51 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-15 04:25:51 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-15 04:25:51 (1943) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-15 04:25:59 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-15 04:25:59 (1826) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-15 04:25:59 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-15 04:25:59 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9S0f3J_RF0/ea_profile.json
* 2024-05-15 04:26:04 (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/9S0f3J_RF0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-15 04:26:04 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-16 04:25:46 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-16 04:25:46 (7553) [INFO] Newer version of script found. Downloading.
* 2024-05-16 04:25:47 (7562) [INFO] Script update to version 38 successful.
* 2024-05-16 04:25:49 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-16 04:25:53 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-16 04:25:53 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-16 04:25:53 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-16 04:26:02 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-16 04:26:02 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-16 04:26:03 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-16 04:26:03 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CVx3ZJk8_z/ea_profile.json
* 2024-05-16 04:26:07 (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/CVx3ZJk8_z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-16 04:26:07 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-17 04:25:49 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-17 04:25:49 (7748) [INFO] Script is up to date.
* 2024-05-17 04:25:51 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-17 04:25:54 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-17 04:25:54 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-17 04:25:54 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-17 04:26:03 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-17 04:26:03 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-17 04:26:03 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-17 04:26:03 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jsm5QhYHsz/ea_profile.json
* 2024-05-17 04:26:07 (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/jsm5QhYHsz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-17 04:26:07 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-18 04:26:42 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-18 04:26:43 (7748) [INFO] Script is up to date.
* 2024-05-18 04:26:45 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-18 04:26:49 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-18 04:26:49 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-18 04:26:49 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-18 04:26:58 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-18 04:26:58 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-18 04:26:58 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-18 04:26:58 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/igOMhAjOr_/ea_profile.json
* 2024-05-18 04:27:02 (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/igOMhAjOr_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-18 04:27:02 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-19 04:26:49 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-19 04:26:49 (7748) [INFO] Script is up to date.
* 2024-05-19 04:26:52 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-19 04:26:56 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-19 04:26:56 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-19 04:26:56 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-19 04:27:04 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-19 04:27:04 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-19 04:27:04 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-19 04:27:04 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rFLY4BQkJ7/ea_profile.json
* 2024-05-19 04:27: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/rFLY4BQkJ7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-19 04:27:08 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-20 04:25:45 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-20 04:25:45 (7748) [INFO] Script is up to date.
* 2024-05-20 04:25:47 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-20 04:25:50 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-20 04:25:50 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-20 04:25:50 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-20 04:25:58 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-20 04:25:58 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-20 04:25:58 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-20 04:25:58 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XJyNLvw66Z/ea_profile.json
* 2024-05-20 04:26:03 (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/XJyNLvw66Z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-20 04:26:03 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-21 04:26:46 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-21 04:26:46 (7748) [INFO] Script is up to date.
* 2024-05-21 04:26:48 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-21 04:26:51 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-21 04:26:51 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-21 04:26:51 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-21 04:26:57 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-21 04:26:57 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-21 04:26:58 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-21 04:26:58 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/G3t4IBumIn/ea_profile.json
* 2024-05-21 04:27:01 (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/G3t4IBumIn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-21 04:27:01 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-22 04:25:51 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-22 04:25:51 (7748) [INFO] Script is up to date.
* 2024-05-22 04:25:53 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-22 04:25:57 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-22 04:25:57 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-22 04:25:57 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-22 04:26:04 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-22 04:26:04 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-22 04:26:05 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-22 04:26:05 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cro9dW7uqI/ea_profile.json
* 2024-05-22 04:26:09 (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/cro9dW7uqI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-22 04:26:09 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-23 04:25:57 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-23 04:25:58 (7748) [INFO] Script is up to date.
* 2024-05-23 04:26:00 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-23 04:26:04 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-23 04:26:04 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-23 04:26:04 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-23 04:26:14 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-23 04:26:14 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-23 04:26:14 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-23 04:26:14 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CR2H6Hzi6B/ea_profile.json
* 2024-05-23 04:26:18 (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/CR2H6Hzi6B/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-23 04:26:18 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-24 04:25:49 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-24 04:25:49 (7748) [INFO] Script is up to date.
* 2024-05-24 04:25:53 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-24 04:25:56 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-24 04:25:56 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-24 04:25:56 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-24 04:26:05 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-24 04:26:05 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-24 04:26:06 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-24 04:26:06 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aVVyq9Zu4x/ea_profile.json
* 2024-05-24 04:26:11 (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/aVVyq9Zu4x/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-24 04:26:11 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-25 04:26:52 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-25 04:26:52 (7748) [INFO] Script is up to date.
* 2024-05-25 04:26:54 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-25 04:26:58 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-25 04:26:58 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-25 04:26:58 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-25 04:27:05 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-25 04:27:05 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-25 04:27:06 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-25 04:27:06 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MF4deHAqk9/ea_profile.json
* 2024-05-25 04:27: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/MF4deHAqk9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-25 04:27:10 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-26 04:26:40 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-26 04:26:41 (7748) [INFO] Script is up to date.
* 2024-05-26 04:26:43 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-26 04:26:46 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-26 04:26:46 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-26 04:26:46 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-26 04:26:54 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-26 04:26:54 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-26 04:26:54 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-26 04:26:54 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NrF4i_j0nh/ea_profile.json
* 2024-05-26 04:26: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/NrF4i_j0nh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-26 04:26:59 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-27 04:25:53 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-27 04:25:53 (7748) [INFO] Script is up to date.
* 2024-05-27 04:25:55 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-27 04:25:58 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-27 04:25:58 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-27 04:25:58 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-27 04:26:05 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-27 04:26:05 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-27 04:26:05 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-27 04:26:05 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/op4XAwQwyD/ea_profile.json
* 2024-05-27 04:26:09 (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/op4XAwQwyD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-27 04:26:09 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-28 04:25:41 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-28 04:25:41 (7748) [INFO] Script is up to date.
* 2024-05-28 04:25:43 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-28 04:25:46 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-28 04:25:46 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-28 04:25:46 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-28 04:25:54 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-28 04:25:54 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-28 04:25:55 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-28 04:25:55 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/12jmfADIOx/ea_profile.json
* 2024-05-28 04:25: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/12jmfADIOx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-28 04:25:59 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-29 04:25:51 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-29 04:25:51 (7748) [INFO] Script is up to date.
* 2024-05-29 04:25:54 (601) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-29 04:25:57 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-29 04:25:57 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-29 04:25:57 (2050) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-29 04:26:05 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-29 04:26:05 (1933) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-29 04:26:06 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-29 04:26:06 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/h_2PUpYfZO/ea_profile.json
* 2024-05-29 04:26: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/h_2PUpYfZO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-29 04:26:10 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-30 04:25:43 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-30 04:25:43 (7731) [INFO] Newer version of script found. Downloading.
* 2024-05-30 04:25:45 (7740) [INFO] Script update to version 39 successful.
* 2024-05-30 04:25:48 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-05-30 04:25:48 (6568) [INFO] 
* 2024-05-30 04:25:49 (6581) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:50 (6598) [INFO] 
* 2024-05-30 04:25:50 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-30 04:25:54 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-30 04:25:54 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-30 04:25:54 (2099) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-30 04:26:03 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-30 04:26:03 (1982) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-30 04:26:04 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-30 04:26:04 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SMnHgp0e5q/ea_profile.json
* 2024-05-30 04:26: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/SMnHgp0e5q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-05-30 04:26:08 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-31 04:25:47 (7795) [INFO] Self-update of script version 39 requested.
* 2024-05-31 04:25:47 (7817) [INFO] Script is up to date.
* 2024-05-31 04:25:48 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-05-31 04:25:48 (6568) [INFO] 
* 2024-05-31 04:25:49 (6581) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:49 (6598) [INFO] 
* 2024-05-31 04:25:49 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-05-31 04:25:52 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-05-31 04:25:52 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-05-31 04:25:52 (2099) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-05-31 04:26:01 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-31 04:26:01 (1982) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-05-31 04:26:01 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-31 04:26:01 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y9L39FDaAP/ea_profile.json
* 2024-05-31 04:26: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/y9L39FDaAP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-05-31 04:26:04 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-01 04:26:45 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-01 04:26:45 (7817) [INFO] Script is up to date.
* 2024-06-01 04:26:47 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-01 04:26:47 (6568) [INFO] 
* 2024-06-01 04:26:48 (6581) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:48 (6598) [INFO] 
* 2024-06-01 04:26:49 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-01 04:26:52 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-01 04:26:52 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-01 04:26:52 (2099) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-01 04:27:01 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-01 04:27:01 (1982) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-01 04:27:02 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-01 04:27:02 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7QNjeIE2Ef/ea_profile.json
* 2024-06-01 04:27: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/7QNjeIE2Ef/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-01 04:27:07 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-02 04:26:46 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-02 04:26:46 (7817) [INFO] Script is up to date.
* 2024-06-02 04:26:48 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-02 04:26:48 (6568) [INFO] 
* 2024-06-02 04:26:49 (6581) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:49 (6598) [INFO] 
* 2024-06-02 04:26:50 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-02 04:26:53 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-02 04:26:53 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-02 04:26:53 (2099) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-02 04:27:01 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-02 04:27:01 (1982) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-02 04:27:01 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-02 04:27:01 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/r07Zl3pvHY/ea_profile.json
* 2024-06-02 04:27: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/r07Zl3pvHY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-02 04:27:05 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-03 04:25:49 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-03 04:25:49 (7817) [INFO] Script is up to date.
* 2024-06-03 04:25:51 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-03 04:25:51 (6568) [INFO] 
* 2024-06-03 04:25:52 (6581) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:52 (6598) [INFO] 
* 2024-06-03 04:25:53 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-03 04:25:55 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-03 04:25:55 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-03 04:25:55 (2099) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-03 04:26:02 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-03 04:26:02 (1982) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-03 04:26:03 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-03 04:26:03 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OwUo8Khfty/ea_profile.json
* 2024-06-03 04:26:09 (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/OwUo8Khfty/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-03 04:26:09 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-04 04:25:42 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-04 04:25:42 (7817) [INFO] Script is up to date.
* 2024-06-04 04:25:43 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-04 04:25:43 (6568) [INFO] 
* 2024-06-04 04:25:44 (6581) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:44 (6598) [INFO] 
* 2024-06-04 04:25:44 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-04 04:25:47 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-04 04:25:47 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-04 04:25:47 (2099) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-04 04:25:55 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-04 04:25:55 (1982) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-04 04:25:55 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-04 04:25:55 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gAyT0G7Mbl/ea_profile.json
* 2024-06-04 04:25:59 (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/gAyT0G7Mbl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-04 04:25:59 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-05 04:25:49 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-05 04:25:50 (7817) [INFO] Script is up to date.
* 2024-06-05 04:25:52 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-05 04:25:52 (6568) [INFO] 
* 2024-06-05 04:25:53 (6581) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:53 (6598) [INFO] 
* 2024-06-05 04:25:53 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-05 04:25:57 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-05 04:25:57 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-05 04:25:57 (2099) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-05 04:26:04 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-05 04:26:04 (1982) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-05 04:26:05 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-05 04:26:05 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pYKDae5Bh0/ea_profile.json
* 2024-06-05 04:26: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/pYKDae5Bh0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-05 04:26:10 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-06 04:25:51 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-06 04:25:51 (7800) [INFO] Newer version of script found. Downloading.
* 2024-06-06 04:25:52 (7809) [INFO] Script update to version 40 successful.
* 2024-06-06 04:25:54 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-06 04:25:54 (6580) [INFO] 
* 2024-06-06 04:25:55 (6593) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:55 (6610) [INFO] 
* 2024-06-06 04:25:56 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-06 04:25:59 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-06 04:25:59 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-06 04:25:59 (2111) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-06 04:26:08 (1982) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-06 04:26:08 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-06 04:26:08 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-06 04:26:08 (6580) [INFO] 
* 2024-06-06 04:26:08 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-06 04:26:08 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-06 04:26:08 (6593) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-06 04:26:08 (6593) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-06 04:26:08 (6593) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-06 04:26:08 (6593) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-06 04:26:08 (6593) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-06 04:26:08 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-06 04:26:08 (6593) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-06 04:26:08 (6610) [INFO] 
* 2024-06-06 04:26:15 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-06 04:26:15 (1993) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-06 04:26:16 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-06 04:26:16 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hdBiWTPE_3/ea_profile.json
* 2024-06-06 04:26:21 (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/hdBiWTPE_3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-06 04:26:21 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-07 04:25:52 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-07 04:25:53 (7829) [INFO] Script is up to date.
* 2024-06-07 04:25:55 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-07 04:25:55 (6580) [INFO] 
* 2024-06-07 04:25:56 (6593) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:56 (6610) [INFO] 
* 2024-06-07 04:25:57 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-07 04:26:00 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-07 04:26:00 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-07 04:26:00 (2111) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-07 04:26:08 (1982) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-07 04:26:08 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-07 04:26:08 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-07 04:26:08 (6580) [INFO] 
* 2024-06-07 04:26:09 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-07 04:26:09 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-07 04:26:09 (6593) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-07 04:26:09 (6593) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-07 04:26:09 (6593) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-07 04:26:09 (6593) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-07 04:26:09 (6593) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-07 04:26:09 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-07 04:26:09 (6593) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-07 04:26:09 (6610) [INFO] 
* 2024-06-07 04:26:16 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-07 04:26:16 (1993) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-07 04:26:17 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-07 04:26:17 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gM5GD44StH/ea_profile.json
* 2024-06-07 04:26: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/gM5GD44StH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-07 04:26:22 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-08 04:26:40 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-08 04:26:40 (7829) [INFO] Script is up to date.
* 2024-06-08 04:26:42 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-08 04:26:42 (6580) [INFO] 
* 2024-06-08 04:26:43 (6593) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:43 (6610) [INFO] 
* 2024-06-08 04:26:44 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-08 04:26:48 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-08 04:26:48 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-08 04:26:48 (2111) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-08 04:27:04 (1982) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Unknown error"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Unknown error"
* 2024-06-08 04:27:04 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-08 04:27:04 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-08 04:27:04 (6580) [INFO] 
* 2024-06-08 04:27:04 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-08 04:27:04 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-08 04:27:04 (6593) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-08 04:27:04 (6593) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-08 04:27:04 (6593) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-08 04:27:04 (6593) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-08 04:27:04 (6593) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-08 04:27:04 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-08 04:27:04 (6593) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-08 04:27:04 (6610) [INFO] 
* 2024-06-08 04:27:12 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-08 04:27:12 (1993) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-08 04:27:12 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-08 04:27:12 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UxgORLNgTV/ea_profile.json
* 2024-06-08 04:27:17 (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/UxgORLNgTV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-08 04:27:17 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-09 04:26:39 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-09 04:26:39 (7829) [INFO] Script is up to date.
* 2024-06-09 04:26:43 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-09 04:26:43 (6580) [INFO] 
* 2024-06-09 04:26:44 (6593) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:44 (6610) [INFO] 
* 2024-06-09 04:26:45 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-09 04:26:48 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-09 04:26:48 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-09 04:26:48 (2111) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-09 04:26:57 (1982) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-09 04:26:57 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-09 04:26:57 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-09 04:26:57 (6580) [INFO] 
* 2024-06-09 04:26:58 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-09 04:26:58 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-09 04:26:58 (6593) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-09 04:26:58 (6593) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-09 04:26:58 (6593) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-09 04:26:58 (6593) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-09 04:26:58 (6593) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-09 04:26:58 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-09 04:26:58 (6593) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-09 04:26:58 (6610) [INFO] 
* 2024-06-09 04:27:07 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-09 04:27:07 (1993) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-09 04:27:08 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-09 04:27:08 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/65WmT4L8ap/ea_profile.json
* 2024-06-09 04:27:13 (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/65WmT4L8ap/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-09 04:27:13 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-10 04:25:57 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-10 04:25:57 (7829) [INFO] Script is up to date.
* 2024-06-10 04:25:59 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-10 04:25:59 (6580) [INFO] 
* 2024-06-10 04:26:00 (6593) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:00 (6610) [INFO] 
* 2024-06-10 04:26:01 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-10 04:26:04 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-10 04:26:04 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-10 04:26:04 (2111) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-10 04:26:13 (1982) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-10 04:26:13 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-10 04:26:13 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-10 04:26:13 (6580) [INFO] 
* 2024-06-10 04:26:13 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-10 04:26:14 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-10 04:26:14 (6593) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-10 04:26:14 (6593) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-10 04:26:14 (6593) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-10 04:26:14 (6593) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-10 04:26:14 (6593) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-10 04:26:14 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-10 04:26:14 (6593) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-10 04:26:14 (6610) [INFO] 
* 2024-06-10 04:26:23 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-10 04:26:23 (1993) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-10 04:26:23 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-10 04:26:23 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Z5r4SEWwIE/ea_profile.json
* 2024-06-10 04:26: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/Z5r4SEWwIE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-10 04:26:28 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-11 04:25:52 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-11 04:25:53 (7829) [INFO] Script is up to date.
* 2024-06-11 04:25:54 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-11 04:25:54 (6580) [INFO] 
* 2024-06-11 04:25:55 (6593) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:55 (6610) [INFO] 
* 2024-06-11 04:25:56 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-11 04:25:59 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-11 04:25:59 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-11 04:25:59 (2111) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-11 04:26:10 (1982) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-11 04:26:10 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-11 04:26:10 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-11 04:26:10 (6580) [INFO] 
* 2024-06-11 04:26:10 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-11 04:26:11 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-11 04:26:11 (6593) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-11 04:26:11 (6593) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-11 04:26:11 (6593) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-11 04:26:11 (6593) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-11 04:26:11 (6593) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-11 04:26:11 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-11 04:26:11 (6593) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-11 04:26:11 (6610) [INFO] 
* 2024-06-11 04:26:20 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-11 04:26:20 (1993) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-11 04:26:20 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-11 04:26:20 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gTGpv3fi_o/ea_profile.json
* 2024-06-11 04:26: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/gTGpv3fi_o/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-11 04:26:24 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-12 04:27:06 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-12 04:27:06 (7829) [INFO] Script is up to date.
* 2024-06-12 04:27:09 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-12 04:27:09 (6580) [INFO] 
* 2024-06-12 04:27:12 (6593) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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-12 04:27:12 (6610) [INFO] 
* 2024-06-12 04:27:13 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-12 04:27:18 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-12 04:27:18 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-12 04:27:18 (2111) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-12 04:27:27 (1982) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-12 04:27:27 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-12 04:27:27 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-12 04:27:27 (6580) [INFO] 
* 2024-06-12 04:27:27 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-12 04:27:28 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-12 04:27:28 (6593) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-12 04:27:28 (6593) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-12 04:27:28 (6593) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-12 04:27:28 (6593) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-12 04:27:28 (6593) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-12 04:27:28 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-12 04:27:28 (6593) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-12 04:27:28 (6610) [INFO] 
* 2024-06-12 04:27:36 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-12 04:27:36 (1993) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-12 04:27:36 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-12 04:27:36 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1wFefWtYbb/ea_profile.json
* 2024-06-12 04:27:41 (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/1wFefWtYbb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-12 04:27:41 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-13 04:25:50 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-13 04:25:51 (7812) [INFO] Newer version of script found. Downloading.
* 2024-06-13 04:25:52 (7821) [INFO] Script update to version 41 successful.
* 2024-06-13 04:25:53 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-13 04:25:53 (6591) [INFO] 
* 2024-06-13 04:25:54 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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-13 04:25:54 (6621) [INFO] 
* 2024-06-13 04:25:55 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-13 04:25:58 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-13 04:25:58 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-13 04:25:58 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-13 04:26:08 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-13 04:26:08 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-13 04:26:08 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-13 04:26:08 (6591) [INFO] 
* 2024-06-13 04:26:08 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-13 04:26:08 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-13 04:26:08 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-13 04:26:08 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-13 04:26:08 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-13 04:26:08 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-13 04:26:08 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-13 04:26:08 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-13 04:26:08 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-13 04:26:08 (6621) [INFO] 
* 2024-06-13 04:26:15 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-13 04:26:15 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-13 04:26:16 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-13 04:26:16 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5_gx9372eh/ea_profile.json
* 2024-06-13 04:26:20 (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/5_gx9372eh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-13 04:26:20 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-14 04:25:53 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-14 04:25:54 (7840) [INFO] Script is up to date.
* 2024-06-14 04:25:55 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-14 04:25:55 (6591) [INFO] 
* 2024-06-14 04:25:56 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:57 (6621) [INFO] 
* 2024-06-14 04:25:57 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-14 04:26:00 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-14 04:26:00 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-14 04:26:00 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-14 04:26:09 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-14 04:26:09 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-14 04:26:09 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-14 04:26:09 (6591) [INFO] 
* 2024-06-14 04:26:10 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-14 04:26:10 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-14 04:26:10 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-14 04:26:10 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-14 04:26:10 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-14 04:26:10 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-14 04:26:10 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-14 04:26:10 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-14 04:26:10 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-14 04:26:10 (6621) [INFO] 
* 2024-06-14 04:26:20 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-14 04:26:20 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-14 04:26:20 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-14 04:26:21 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZDRs0vN6T7/ea_profile.json
* 2024-06-14 04:26:26 (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/ZDRs0vN6T7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-14 04:26:26 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-15 04:26:43 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-15 04:26:43 (7840) [INFO] Script is up to date.
* 2024-06-15 04:26:47 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-15 04:26:47 (6591) [INFO] 
* 2024-06-15 04:26:50 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:50 (6621) [INFO] 
* 2024-06-15 04:26:52 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-15 04:26:56 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-15 04:26:56 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-15 04:26:56 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-15 04:27:06 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-15 04:27:06 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-15 04:27:06 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-15 04:27:06 (6591) [INFO] 
* 2024-06-15 04:27:06 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-15 04:27:06 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-15 04:27:06 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-15 04:27:06 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-15 04:27:06 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-15 04:27:06 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-15 04:27:06 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-15 04:27:06 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-15 04:27:06 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-15 04:27:06 (6621) [INFO] 
* 2024-06-15 04:27:15 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-15 04:27:15 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-15 04:27:16 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-15 04:27:16 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nesFzJhRxt/ea_profile.json
* 2024-06-15 04:27:20 (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/nesFzJhRxt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-15 04:27:20 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-16 04:26:50 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-16 04:26:50 (7840) [INFO] Script is up to date.
* 2024-06-16 04:26:54 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-16 04:26:54 (6591) [INFO] 
* 2024-06-16 04:26:55 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:55 (6621) [INFO] 
* 2024-06-16 04:26:56 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-16 04:26:59 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-16 04:26:59 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-16 04:26:59 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-16 04:27:08 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-16 04:27:08 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-16 04:27:08 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-16 04:27:08 (6591) [INFO] 
* 2024-06-16 04:27:08 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-16 04:27:08 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-16 04:27:08 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-16 04:27:08 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-16 04:27:08 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-16 04:27:08 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-16 04:27:08 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-16 04:27:09 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-16 04:27:09 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-16 04:27:09 (6621) [INFO] 
* 2024-06-16 04:27:17 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-16 04:27:17 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-16 04:27:17 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-16 04:27:17 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OO1DO_iBmj/ea_profile.json
* 2024-06-16 04:27: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/OO1DO_iBmj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-16 04:27:22 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-17 04:25:54 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-17 04:25:54 (7840) [INFO] Script is up to date.
* 2024-06-17 04:25:56 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-17 04:25:56 (6591) [INFO] 
* 2024-06-17 04:25:58 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:58 (6621) [INFO] 
* 2024-06-17 04:25:59 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-17 04:26:03 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-17 04:26:03 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-17 04:26:03 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-17 04:26:12 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-17 04:26:12 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-17 04:26:12 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-17 04:26:12 (6591) [INFO] 
* 2024-06-17 04:26:13 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-17 04:26:13 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-17 04:26:13 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-17 04:26:13 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-17 04:26:13 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-17 04:26:13 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-17 04:26:13 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-17 04:26:13 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-17 04:26:13 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-17 04:26:13 (6621) [INFO] 
* 2024-06-17 04:26:22 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-17 04:26:22 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-17 04:26:22 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-17 04:26:22 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jiCyz76JYw/ea_profile.json
* 2024-06-17 04:26:26 (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/jiCyz76JYw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-17 04:26:26 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-18 04:25:50 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-18 04:25:50 (7840) [INFO] Script is up to date.
* 2024-06-18 04:25:55 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-18 04:25:55 (6591) [INFO] 
* 2024-06-18 04:25:57 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:57 (6621) [INFO] 
* 2024-06-18 04:25:58 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-18 04:26:02 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-18 04:26:02 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-18 04:26:02 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-18 04:26:12 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-18 04:26:12 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-18 04:26:12 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-18 04:26:12 (6591) [INFO] 
* 2024-06-18 04:26:13 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-18 04:26:13 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-18 04:26:13 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-18 04:26:13 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-18 04:26:13 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-18 04:26:13 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-18 04:26:13 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-18 04:26:13 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-18 04:26:13 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-18 04:26:13 (6621) [INFO] 
* 2024-06-18 04:26:21 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-18 04:26:21 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-18 04:26:22 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-18 04:26:22 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EAildxWNQH/ea_profile.json
* 2024-06-18 04:26:26 (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/EAildxWNQH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-18 04:26:26 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-19 04:26:07 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-19 04:26:07 (7840) [INFO] Script is up to date.
* 2024-06-19 04:26:10 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-19 04:26:10 (6591) [INFO] 
* 2024-06-19 04:26:12 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:12 (6621) [INFO] 
* 2024-06-19 04:26:13 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-19 04:26:16 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-19 04:26:16 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-19 04:26:16 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-19 04:26:25 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-19 04:26:25 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-19 04:26:25 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-19 04:26:25 (6591) [INFO] 
* 2024-06-19 04:26:25 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-19 04:26:25 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-19 04:26:25 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-19 04:26:25 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-19 04:26:25 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-19 04:26:25 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-19 04:26:25 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-19 04:26:25 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-19 04:26:25 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-19 04:26:25 (6621) [INFO] 
* 2024-06-19 04:26:33 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-19 04:26:33 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-19 04:26:33 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-19 04:26:33 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AV2XbgGnRG/ea_profile.json
* 2024-06-19 04:26:38 (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/AV2XbgGnRG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-19 04:26:38 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-20 04:25:48 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-20 04:25:49 (7840) [INFO] Script is up to date.
* 2024-06-20 04:25:51 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-20 04:25:51 (6591) [INFO] 
* 2024-06-20 04:25:53 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:53 (6621) [INFO] 
* 2024-06-20 04:25:53 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-20 04:25:57 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-20 04:25:57 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-20 04:25:57 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-20 04:26:05 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-20 04:26:05 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-20 04:26:05 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-20 04:26:05 (6591) [INFO] 
* 2024-06-20 04:26:05 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-20 04:26:05 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-20 04:26:05 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-20 04:26:05 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-20 04:26:05 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-20 04:26:05 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-20 04:26:05 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-20 04:26:05 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-20 04:26:05 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-20 04:26:05 (6621) [INFO] 
* 2024-06-20 04:26:13 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-20 04:26:13 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-20 04:26:13 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-20 04:26:13 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9CQRYG40FI/ea_profile.json
* 2024-06-20 04:26:18 (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/9CQRYG40FI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-20 04:26:18 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-21 04:25:53 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-21 04:25:53 (7840) [INFO] Script is up to date.
* 2024-06-21 04:25:55 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-21 04:25:55 (6591) [INFO] 
* 2024-06-21 04:25:57 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:57 (6621) [INFO] 
* 2024-06-21 04:25:58 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-21 04:26:02 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-21 04:26:02 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-21 04:26:02 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-21 04:26:11 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-21 04:26:11 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-21 04:26:11 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-21 04:26:11 (6591) [INFO] 
* 2024-06-21 04:26:11 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-21 04:26:11 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-21 04:26:11 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-21 04:26:11 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-21 04:26:11 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-21 04:26:11 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-21 04:26:11 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-21 04:26:11 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-21 04:26:11 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-21 04:26:11 (6621) [INFO] 
* 2024-06-21 04:26:20 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-21 04:26:20 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-21 04:26:20 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-21 04:26:20 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xYHTJSyJjm/ea_profile.json
* 2024-06-21 04:26:25 (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/xYHTJSyJjm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-21 04:26:25 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-22 04:26:50 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-22 04:26:50 (7840) [INFO] Script is up to date.
* 2024-06-22 04:26:54 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-22 04:26:54 (6591) [INFO] 
* 2024-06-22 04:26:56 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:56 (6621) [INFO] 
* 2024-06-22 04:26:56 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-22 04:27:01 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-22 04:27:01 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-22 04:27:01 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-22 04:27:11 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-22 04:27:11 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-22 04:27:11 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-22 04:27:11 (6591) [INFO] 
* 2024-06-22 04:27:11 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-22 04:27:11 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-22 04:27:11 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-22 04:27:11 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-22 04:27:11 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-22 04:27:11 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-22 04:27:11 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-22 04:27:11 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-22 04:27:11 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-22 04:27:11 (6621) [INFO] 
* 2024-06-22 04:27:20 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-22 04:27:20 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-22 04:27:21 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-22 04:27:21 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IUSOLrPesx/ea_profile.json
* 2024-06-22 04:27:25 (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/IUSOLrPesx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-22 04:27:25 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-23 04:27:55 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-23 04:27:55 (7840) [INFO] Script is up to date.
* 2024-06-23 04:27:58 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-23 04:27:58 (6591) [INFO] 
* 2024-06-23 04:27:59 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:27:59 (6621) [INFO] 
* 2024-06-23 04:27:59 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-23 04:28:02 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-23 04:28:02 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-23 04:28:02 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-23 04:28:22 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-23 04:28:22 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-23 04:28:22 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-23 04:28:22 (6591) [INFO] 
* 2024-06-23 04:28:22 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-23 04:28:22 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-23 04:28:22 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-23 04:28:22 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-23 04:28:22 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-23 04:28:22 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-23 04:28:22 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-23 04:28:22 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-23 04:28:22 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-23 04:28:22 (6621) [INFO] 
* 2024-06-23 04:28:34 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-23 04:28:34 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-23 04:28:34 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-23 04:28:34 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MNYux2y6nc/ea_profile.json
* 2024-06-23 04:28:40 (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/MNYux2y6nc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-23 04:28:40 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-24 04:25:46 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-24 04:25:46 (7840) [INFO] Script is up to date.
* 2024-06-24 04:25:48 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-24 04:25:48 (6591) [INFO] 
* 2024-06-24 04:25:49 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:49 (6621) [INFO] 
* 2024-06-24 04:25:50 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-24 04:25:53 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-24 04:25:53 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-24 04:25:53 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-24 04:26:01 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-24 04:26:01 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-24 04:26:01 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-24 04:26:01 (6591) [INFO] 
* 2024-06-24 04:26:02 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-24 04:26:02 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-24 04:26:02 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-24 04:26:02 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-24 04:26:02 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-24 04:26:02 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-24 04:26:02 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-24 04:26:02 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-24 04:26:02 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-24 04:26:02 (6621) [INFO] 
* 2024-06-24 04:26:09 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-24 04:26:09 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-24 04:26:09 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-24 04:26:09 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nkPwZM77bH/ea_profile.json
* 2024-06-24 04:26: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/nkPwZM77bH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-24 04:26:14 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-25 04:25:57 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-25 04:25:57 (7840) [INFO] Script is up to date.
* 2024-06-25 04:25:59 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-25 04:25:59 (6591) [INFO] 
* 2024-06-25 04:26:00 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:00 (6621) [INFO] 
* 2024-06-25 04:26:01 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-25 04:26:05 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-25 04:26:05 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-25 04:26:05 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-25 04:26:17 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Unknown error"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Unknown error"
* 2024-06-25 04:26:17 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-25 04:26:17 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-25 04:26:17 (6591) [INFO] 
* 2024-06-25 04:26:17 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-25 04:26:18 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-25 04:26:18 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-25 04:26:18 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-25 04:26:18 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-25 04:26:18 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-25 04:26:18 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-25 04:26:18 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-25 04:26:18 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-25 04:26:18 (6621) [INFO] 
* 2024-06-25 04:26:28 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-25 04:26:28 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-25 04:26:28 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-25 04:26:28 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7ZpYeErW1R/ea_profile.json
* 2024-06-25 04:26:33 (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/7ZpYeErW1R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-25 04:26:33 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-26 04:26:50 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-26 04:26:50 (7840) [INFO] Script is up to date.
* 2024-06-26 04:26:53 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-26 04:26:53 (6591) [INFO] 
* 2024-06-26 04:26:55 (6604) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:55 (6621) [INFO] 
* 2024-06-26 04:26:56 (604) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-26 04:27:01 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-26 04:27:01 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-26 04:27:01 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-26 04:27:10 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-26 04:27:10 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-26 04:27:10 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-26 04:27:10 (6591) [INFO] 
* 2024-06-26 04:27:11 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-26 04:27:11 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-26 04:27:11 (6604) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-26 04:27:11 (6604) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-26 04:27:11 (6604) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-26 04:27:11 (6604) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-26 04:27:11 (6604) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-26 04:27:11 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-26 04:27:11 (6604) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-26 04:27:11 (6621) [INFO] 
* 2024-06-26 04:27:20 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-26 04:27:20 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-26 04:27:20 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-26 04:27:20 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sMeyAZXGzo/ea_profile.json
* 2024-06-26 04:27:25 (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/sMeyAZXGzo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-26 04:27:25 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-27 04:25:47 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-27 04:25:47 (7823) [INFO] Newer version of script found. Downloading.
* 2024-06-27 04:25:48 (7832) [INFO] Script update to version 43 successful.
* 2024-06-27 04:25:51 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-27 04:25:51 (6738) [INFO] 
* 2024-06-27 04:25:52 (6751) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:52 (6768) [INFO] 
* 2024-06-27 04:25:53 (607) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-27 04:25:57 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-27 04:25:57 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-27 04:25:57 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-27 04:26:07 (1985) [WARN] Initial run of "yum makecache" failed: https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-27 04:26:07 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-27 04:26:07 (6737) [INFO] Running: /usr/bin/yum clean all
* 2024-06-27 04:26:07 (6738) [INFO] 
* 2024-06-27 04:26:08 (6751) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-27 04:26:08 (6751) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-27 04:26:08 (6751) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-27 04:26:08 (6751) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-27 04:26:08 (6751) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-27 04:26:08 (6751) [INFO]               : letsencrypt-cpanel remi-safe updates wp-toolkit-cpanel
* 2024-06-27 04:26:08 (6751) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-06-27 04:26:08 (6751) [INFO] Cleaning up list of fastest mirrors
* 2024-06-27 04:26:08 (6751) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-06-27 04:26:08 (6768) [INFO] 
* 2024-06-27 04:26:18 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-27 04:26:18 (1996) [ERROR] https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
Trying other mirror.


 One of the configured repositories failed (Let's Encrypt for cPanel),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=letsencrypt-cpanel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable letsencrypt-cpanel
        or
            subscription-manager repos --disable=letsencrypt-cpanel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=letsencrypt-cpanel.skip_if_unavailable=true

failure: repodata/repomd.xml from letsencrypt-cpanel: [Errno 256] No more mirrors to try.
https://r.cpanel.fleetssl.com/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: r.cpanel.fleetssl.com; Name or service not known"
* 2024-06-27 04:26:19 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-27 04:26:20 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6qBz4SjKjS/ea_profile.json
* 2024-06-27 04:26:25 (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/6qBz4SjKjS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-27 04:26:25 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-28 04:25:39 (7972) [INFO] Self-update of script version 43 requested.
* 2024-06-28 04:25:39 (7994) [INFO] Script is up to date.
* 2024-06-28 04:25:40 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-28 04:25:40 (6738) [INFO] 
* 2024-06-28 04:25:41 (6751) [INFO] {"items": "7.6.4", "version": "7.6.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:41 (6768) [INFO] 
* 2024-06-28 04:25:42 (607) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-28 04:25:44 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-28 04:25:44 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-28 04:25:44 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-28 04:26:34 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-28 04:26:34 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5mhAplqKdT/ea_profile.json
* 2024-06-28 04:26:35 (5904) [INFO] Backed up EA4 profile to /tmp/5mhAplqKdT/ea_profile.json
* 2024-06-28 04:26:37 (207) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-06-28 04:26:37 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-28 04:26:37 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-29 04:32:13 (7972) [INFO] Self-update of script version 43 requested.
* 2024-06-29 04:32:13 (7994) [INFO] Script is up to date.
* 2024-06-29 04:32:14 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-29 04:32:14 (6738) [INFO] 
* 2024-06-29 04:32:17 (6751) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:32:17 (6768) [INFO] 
* 2024-06-29 04:32:17 (607) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-29 04:32:19 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-29 04:32:19 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-29 04:32:19 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-29 04:32:47 (1985) [WARN] Initial run of "yum makecache" failed: https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: download.imunify360.com; Unknown error"
Trying other mirror.
* 2024-06-29 04:32:47 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-29 04:32:47 (6737) [INFO] Running: /usr/bin/yum clean all
* 2024-06-29 04:32:47 (6738) [INFO] 
* 2024-06-29 04:32:47 (6751) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-29 04:32:47 (6751) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-06-29 04:32:47 (6751) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-06-29 04:32:47 (6751) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-06-29 04:32:47 (6751) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-06-29 04:32:47 (6751) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-06-29 04:32:47 (6751) [INFO]               : zabbix zabbix-non-supported
* 2024-06-29 04:32:48 (6751) [INFO] Cleaning up list of fastest mirrors
* 2024-06-29 04:32:48 (6751) [INFO] Other repos take up 4.1 M of disk space (use --verbose for details)
* 2024-06-29 04:32:48 (6768) [INFO] 
* 2024-06-29 04:33:36 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-29 04:33:36 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bYSXTt9S_I/ea_profile.json
* 2024-06-29 04:33:37 (5904) [INFO] Backed up EA4 profile to /tmp/bYSXTt9S_I/ea_profile.json
* 2024-06-29 04:33:38 (207) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-06-29 04:33:39 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-29 04:33:39 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-30 04:27:16 (7972) [INFO] Self-update of script version 43 requested.
* 2024-06-30 04:27:16 (7994) [INFO] Script is up to date.
* 2024-06-30 04:27:17 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-30 04:27:17 (6738) [INFO] 
* 2024-06-30 04:27:20 (6751) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:27:20 (6768) [INFO] 
* 2024-06-30 04:27:21 (607) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-06-30 04:27:23 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-06-30 04:27:23 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-06-30 04:27:23 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-06-30 04:27:38 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-30 04:27:39 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gip3ANBxGM/ea_profile.json
* 2024-06-30 04:27:40 (5904) [INFO] Backed up EA4 profile to /tmp/gip3ANBxGM/ea_profile.json
* 2024-06-30 04:27:41 (207) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-06-30 04:27:42 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-30 04:27:42 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-01 04:26:15 (7972) [INFO] Self-update of script version 43 requested.
* 2024-07-01 04:26:15 (7994) [INFO] Script is up to date.
* 2024-07-01 04:26:17 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-01 04:26:17 (6738) [INFO] 
* 2024-07-01 04:26:19 (6751) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:19 (6768) [INFO] 
* 2024-07-01 04:26:20 (607) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-01 04:26:21 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-01 04:26:21 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-01 04:26:21 (2122) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-01 04:26:35 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-01 04:26:36 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EgF7Ah0dFl/ea_profile.json
* 2024-07-01 04:26:37 (5904) [INFO] Backed up EA4 profile to /tmp/EgF7Ah0dFl/ea_profile.json
* 2024-07-01 04:26:38 (207) [WARN] *** Elevation Blocker detected: ***
We have detected that your server is hosted by "OVH SA" company.

Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH.
When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process.

Once you have disabled the monitoring system (or confirm this message does not apply to you),
please touch that file and continue the elevation pricess.

> touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate

You can read more about this issue:
URL: https://github.com/cpanel/elevate/issues/176
OVH Monitoring Documentation: https://support.us.ovhcloud.com/hc/en-us/articles/115001821044-Overview-of-OVHcloud-Monitoring-on-Dedicated-Servers

* 2024-07-01 04:26:38 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-07-01 04:26:38 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-02 04:26:42 (7972) [INFO] Self-update of script version 43 requested.
* 2024-07-02 04:26:42 (7977) [INFO] Newer version of script found. Downloading.
* 2024-07-02 04:26:43 (7986) [INFO] Script update to version 44 successful.
* 2024-07-02 04:26:45 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-02 04:26:45 (6800) [INFO] 
* 2024-07-02 04:26:49 (6813) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:50 (6830) [INFO] 
* 2024-07-02 04:26:50 (608) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-02 04:26:52 (2101) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-02 04:26:52 (2101) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-02 04:26:52 (2123) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-02 04:26:59 (1986) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-02 04:26:59 (1987) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-02 04:26:59 (6799) [INFO] Running: /usr/bin/yum clean all
* 2024-07-02 04:26:59 (6800) [INFO] 
* 2024-07-02 04:26:59 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-02 04:26:59 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-02 04:26:59 (6813) [INFO]               : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-07-02 04:26:59 (6813) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-07-02 04:26:59 (6813) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-07-02 04:26:59 (6813) [INFO]               : remi-safe updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-02 04:26:59 (6813) [INFO]               : zabbix zabbix-non-supported
* 2024-07-02 04:26:59 (6813) [INFO] Cleaning up list of fastest mirrors
* 2024-07-02 04:26:59 (6813) [INFO] Other repos take up 4.1 M of disk space (use --verbose for details)
* 2024-07-02 04:26:59 (6830) [INFO] 
* 2024-07-02 04:27:06 (1996) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-02 04:27:06 (1997) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-02 04:27:06 (1046) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-02 04:27:07 (5943) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BMULrTal1Y/ea_profile.json
* 2024-07-02 04:27:09 (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/BMULrTal1Y/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945.
* 2024-07-02 04:27:09 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-03 04:25:39 (8035) [INFO] Self-update of script version 44 requested.
* 2024-07-03 04:25:39 (8057) [INFO] Script is up to date.
* 2024-07-03 04:25:40 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-03 04:25:40 (6800) [INFO] 
* 2024-07-03 04:25:44 (6813) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:44 (6830) [INFO] 
* 2024-07-03 04:25:44 (608) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-03 04:25:46 (2101) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-03 04:25:46 (2101) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-03 04:25:46 (2123) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-03 04:25:46 (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 04:25:46 (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 04:25:46 (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 04:25:46 (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 04:25:46 (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 04:25:46 (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 04:25:55 (1986) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-03 04:25:55 (1987) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-03 04:25:55 (6799) [INFO] Running: /usr/bin/yum clean all
* 2024-07-03 04:25:55 (6800) [INFO] 
* 2024-07-03 04:25:55 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-03 04:25:55 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-03 04:25:55 (6813) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-03 04:25:55 (6813) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-03 04:25:55 (6813) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-03 04:25:55 (6813) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-03 04:25:55 (6813) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-03 04:25:55 (6813) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-03 04:25:55 (6813) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-03 04:25:55 (6813) [INFO] Cleaning up list of fastest mirrors
* 2024-07-03 04:25:55 (6813) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-03 04:25:55 (6830) [INFO] 
* 2024-07-03 04:26:03 (1996) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-03 04:26:03 (1997) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-03 04:26:03 (1046) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-03 04:26:04 (5943) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sDi2hAg1hV/ea_profile.json
* 2024-07-03 04:26:06 (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/sDi2hAg1hV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945.
* 2024-07-03 04:26:06 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-04 04:25:33 (8035) [INFO] Self-update of script version 44 requested.
* 2024-07-04 04:25:33 (8040) [INFO] Newer version of script found. Downloading.
* 2024-07-04 04:25:35 (8049) [INFO] Script update to version 45 successful.
* 2024-07-04 04:25:36 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-04 04:25:36 (6814) [INFO] 
* 2024-07-04 04:25:39 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:39 (6844) [INFO] 
* 2024-07-04 04:25:40 (608) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-04 04:25:41 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-04 04:25:41 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-04 04:25:41 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-04 04:25:41 (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 04:25:41 (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 04:25:41 (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 04:25:41 (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 04:25:41 (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 04:25:41 (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 04:25:46 (1999) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-04 04:25:46 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-04 04:25:46 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-04 04:25:46 (6814) [INFO] 
* 2024-07-04 04:25:46 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-04 04:25:46 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-04 04:25:46 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-04 04:25:46 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-04 04:25:46 (6827) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-04 04:25:46 (6827) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-04 04:25:46 (6827) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-04 04:25:46 (6827) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-04 04:25:46 (6827) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-04 04:25:46 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-04 04:25:46 (6827) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-04 04:25:47 (6844) [INFO] 
* 2024-07-04 04:25:54 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-04 04:25:54 (2010) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-04 04:25:54 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-04 04:25:55 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cRiZT9OIHJ/ea_profile.json
* 2024-07-04 04:25: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/cRiZT9OIHJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-04 04:25:58 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-05 04:25:36 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-05 04:25:36 (8071) [INFO] Script is up to date.
* 2024-07-05 04:25:38 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-05 04:25:38 (6814) [INFO] 
* 2024-07-05 04:25:41 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:41 (6844) [INFO] 
* 2024-07-05 04:25:41 (608) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-05 04:25:43 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-05 04:25:43 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-05 04:25:43 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-05 04:25:43 (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 04:25:43 (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 04:25:43 (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 04:25:43 (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 04:25:43 (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 04:25:43 (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 04:25:50 (1999) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-05 04:25:50 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-05 04:25:50 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-05 04:25:50 (6814) [INFO] 
* 2024-07-05 04:25:50 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-05 04:25:50 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-05 04:25:50 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-05 04:25:50 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-05 04:25:50 (6827) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-05 04:25:50 (6827) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-05 04:25:50 (6827) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-05 04:25:50 (6827) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-05 04:25:50 (6827) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-05 04:25:50 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-05 04:25:50 (6827) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-05 04:25:50 (6844) [INFO] 
* 2024-07-05 04:25:59 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-05 04:25:59 (2010) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-05 04:25:59 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-05 04:26:00 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MrTnCLvbDY/ea_profile.json
* 2024-07-05 04:26:02 (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/MrTnCLvbDY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-05 04:26:02 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-06 04:26:30 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-06 04:26:30 (8071) [INFO] Script is up to date.
* 2024-07-06 04:26:32 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-06 04:26:32 (6814) [INFO] 
* 2024-07-06 04:26:35 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:36 (6844) [INFO] 
* 2024-07-06 04:26:36 (608) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-06 04:26:37 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-06 04:26:37 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-06 04:26:37 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-06 04:26:37 (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 04:26:37 (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 04:26:37 (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 04:26:37 (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 04:26:37 (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 04:26:37 (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 04:26:43 (1999) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-06 04:26:43 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-06 04:26:43 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-06 04:26:43 (6814) [INFO] 
* 2024-07-06 04:26:43 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-06 04:26:43 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-06 04:26:43 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-06 04:26:43 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-06 04:26:43 (6827) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-06 04:26:43 (6827) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-06 04:26:43 (6827) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-06 04:26:43 (6827) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-06 04:26:43 (6827) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-06 04:26:43 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-06 04:26:43 (6827) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-06 04:26:43 (6844) [INFO] 
* 2024-07-06 04:26:48 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-06 04:26:48 (2010) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-06 04:26:48 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-06 04:26:49 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/m7m060AofZ/ea_profile.json
* 2024-07-06 04:26:51 (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/m7m060AofZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-06 04:26:51 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-07 04:26:13 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-07 04:26:13 (8071) [INFO] Script is up to date.
* 2024-07-07 04:26:14 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-07 04:26:14 (6814) [INFO] 
* 2024-07-07 04:26:16 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:16 (6844) [INFO] 
* 2024-07-07 04:26:17 (608) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-07 04:26:18 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-07 04:26:18 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-07 04:26:18 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-07 04:26:18 (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 04:26:18 (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 04:26:18 (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 04:26:18 (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 04:26:18 (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 04:26:18 (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 04:26:25 (1999) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-07 04:26:25 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-07 04:26:25 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-07 04:26:25 (6814) [INFO] 
* 2024-07-07 04:26:25 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-07 04:26:25 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-07 04:26:25 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-07 04:26:25 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-07 04:26:25 (6827) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-07 04:26:25 (6827) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-07 04:26:25 (6827) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-07 04:26:25 (6827) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-07 04:26:25 (6827) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-07 04:26:25 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-07 04:26:25 (6827) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-07 04:26:25 (6844) [INFO] 
* 2024-07-07 04:26:31 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-07 04:26:31 (2010) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-07 04:26:31 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-07 04:26:32 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/o7zUKAgO_a/ea_profile.json
* 2024-07-07 04:26: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/o7zUKAgO_a/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-07 04:26:35 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-08 04:25:36 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-08 04:25:36 (8071) [INFO] Script is up to date.
* 2024-07-08 04:25:37 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-08 04:25:37 (6814) [INFO] 
* 2024-07-08 04:25:40 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:40 (6844) [INFO] 
* 2024-07-08 04:25:41 (608) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-08 04:25:42 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-08 04:25:42 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-08 04:25:42 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-08 04:25:42 (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 04:25:42 (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 04:25:42 (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 04:25:42 (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 04:25:42 (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 04:25:42 (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 04:25:48 (1999) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-08 04:25:48 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-08 04:25:48 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-08 04:25:48 (6814) [INFO] 
* 2024-07-08 04:25:48 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-08 04:25:48 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-08 04:25:48 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-08 04:25:48 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-08 04:25:48 (6827) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-08 04:25:48 (6827) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-08 04:25:48 (6827) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-08 04:25:48 (6827) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-08 04:25:48 (6827) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-08 04:25:48 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-08 04:25:48 (6827) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-08 04:25:48 (6844) [INFO] 
* 2024-07-08 04:25:53 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-08 04:25:53 (2010) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-08 04:25:54 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-08 04:25:55 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QthcBmGJMV/ea_profile.json
* 2024-07-08 04:25:56 (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/QthcBmGJMV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-08 04:25:56 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-09 04:25:38 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-09 04:25:38 (8071) [INFO] Script is up to date.
* 2024-07-09 04:25:41 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-09 04:25:41 (6814) [INFO] 
* 2024-07-09 04:25:45 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:45 (6844) [INFO] 
* 2024-07-09 04:25:46 (608) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-09 04:25:48 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-09 04:25:48 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-09 04:25:48 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-09 04:25:48 (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 04:25:48 (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 04:25:48 (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 04:25:48 (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 04:25:48 (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 04:25:48 (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 04:25:55 (1999) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-09 04:25:55 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-09 04:25:55 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-09 04:25:55 (6814) [INFO] 
* 2024-07-09 04:25:55 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-09 04:25:56 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-09 04:25:56 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-09 04:25:56 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-09 04:25:56 (6827) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-09 04:25:56 (6827) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-09 04:25:56 (6827) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-09 04:25:56 (6827) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-09 04:25:56 (6827) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-09 04:25:56 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-09 04:25:56 (6827) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-09 04:25:56 (6844) [INFO] 
* 2024-07-09 04:26:01 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-09 04:26:01 (2010) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-09 04:26:01 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-09 04:26:02 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mLU4BHKSO2/ea_profile.json
* 2024-07-09 04:26:04 (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/mLU4BHKSO2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-09 04:26:04 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-10 04:25:36 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-10 04:25:36 (8071) [INFO] Script is up to date.
* 2024-07-10 04:25:38 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-10 04:25:38 (6814) [INFO] 
* 2024-07-10 04:25:41 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:41 (6844) [INFO] 
* 2024-07-10 04:25:42 (608) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-10 04:25:43 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-10 04:25:43 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-10 04:25:43 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-10 04:25:43 (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 04:25:43 (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 04:25:43 (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 04:25:43 (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 04:25:43 (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 04:25:43 (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 04:25:49 (1999) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-10 04:25:49 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-10 04:25:49 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-10 04:25:49 (6814) [INFO] 
* 2024-07-10 04:25:49 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-10 04:25:50 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-10 04:25:50 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-10 04:25:50 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-10 04:25:50 (6827) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-10 04:25:50 (6827) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-10 04:25:50 (6827) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-10 04:25:50 (6827) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-10 04:25:50 (6827) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-10 04:25:50 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-10 04:25:50 (6827) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-10 04:25:50 (6844) [INFO] 
* 2024-07-10 04:25:56 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-10 04:25:56 (2010) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-10 04:25:56 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-10 04:25:57 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tHHvljF_Qd/ea_profile.json
* 2024-07-10 04:25:59 (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/tHHvljF_Qd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-10 04:25:59 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-11 04:25:42 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-11 04:25:42 (8054) [INFO] Newer version of script found. Downloading.
* 2024-07-11 04:25:42 (8063) [INFO] Script update to version 46 successful.
* 2024-07-11 04:25:43 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-11 04:25:43 (6847) [INFO] 
* 2024-07-11 04:25:46 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:46 (6877) [INFO] 
* 2024-07-11 04:25:46 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-11 04:25:46 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-11 04:25:46 (6847) [INFO] 
* 2024-07-11 04:25:54 (6877) [INFO] 
* 2024-07-11 04:25:56 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-11 04:25:56 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-11 04:25:56 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-11 04:25:56 (2139) [ERROR] 70 package(s) installed from unsupported YUM repo 'jetapps' from /etc/yum.repos.d/jetapps.repo
* 2024-07-11 04:25:56 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'jetapps-stable' from /etc/yum.repos.d/jetapps.repo
* 2024-07-11 04:25:57 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-11 04:25:57 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-11 04:25:57 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-11 04:25:57 (6847) [INFO] 
* 2024-07-11 04:25:58 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-11 04:25:58 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-11 04:25:58 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-11 04:25:58 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-11 04:25:58 (6860) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-11 04:25:58 (6860) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-11 04:25:58 (6860) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-11 04:25:58 (6860) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-11 04:25:58 (6860) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-11 04:25:58 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-11 04:25:58 (6860) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-11 04:25:58 (6877) [INFO] 
* 2024-07-11 04:26:04 (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 04:26:04 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-11 04:26:04 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-11 04:26:05 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0fFoTn9xdq/ea_profile.json
* 2024-07-11 04:26:06 (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/0fFoTn9xdq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-11 04:26:06 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-12 04:25:39 (8126) [INFO] Self-update of script version 46 requested.
* 2024-07-12 04:25:39 (8131) [INFO] Newer version of script found. Downloading.
* 2024-07-12 04:25:40 (8140) [INFO] Script update to version 47 successful.
* 2024-07-12 04:25:41 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-12 04:25:41 (6849) [INFO] 
* 2024-07-12 04:25:44 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:44 (6879) [INFO] 
* 2024-07-12 04:25:45 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-12 04:25:45 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-12 04:25:45 (6849) [INFO] 
* 2024-07-12 04:25:51 (6879) [INFO] 
* 2024-07-12 04:25:52 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-12 04:25:52 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-12 04:25:52 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-12 04:25:54 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-12 04:25:54 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-12 04:25:54 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-12 04:25:54 (6849) [INFO] 
* 2024-07-12 04:25:55 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-12 04:25:55 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-12 04:25:55 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-12 04:25:55 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-12 04:25:55 (6862) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-12 04:25:55 (6862) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-12 04:25:55 (6862) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-12 04:25:55 (6862) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-12 04:25:55 (6862) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-12 04:25:55 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-12 04:25:55 (6862) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-12 04:25:55 (6879) [INFO] 
* 2024-07-12 04:25:59 (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 04:25:59 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-12 04:25:59 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-12 04:26:00 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nQh7lRp9no/ea_profile.json
* 2024-07-12 04:26:02 (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/nQh7lRp9no/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-12 04:26:02 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-13 04:26:28 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-13 04:26:28 (8150) [INFO] Script is up to date.
* 2024-07-13 04:26:31 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-13 04:26:31 (6849) [INFO] 
* 2024-07-13 04:26:34 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:34 (6879) [INFO] 
* 2024-07-13 04:26:34 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-13 04:26:34 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-13 04:26:34 (6849) [INFO] 
* 2024-07-13 04:26:42 (6879) [INFO] 
* 2024-07-13 04:26:43 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-13 04:26:43 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-13 04:26:43 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-13 04:26:46 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-13 04:26:46 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-13 04:26:46 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-13 04:26:46 (6849) [INFO] 
* 2024-07-13 04:26:47 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-13 04:26:47 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-13 04:26:47 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-13 04:26:47 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-13 04:26:47 (6862) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-13 04:26:47 (6862) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-13 04:26:47 (6862) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-13 04:26:47 (6862) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-13 04:26:47 (6862) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-13 04:26:47 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-13 04:26:47 (6862) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-13 04:26:47 (6879) [INFO] 
* 2024-07-13 04:26:54 (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 04:26:54 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-13 04:26:54 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-13 04:26:55 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BS5IfSUlf6/ea_profile.json
* 2024-07-13 04:26:58 (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/BS5IfSUlf6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-13 04:26:58 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-14 04:26:14 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-14 04:26:14 (8150) [INFO] Script is up to date.
* 2024-07-14 04:26:16 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-14 04:26:16 (6849) [INFO] 
* 2024-07-14 04:26:21 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:21 (6879) [INFO] 
* 2024-07-14 04:26:22 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-14 04:26:22 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-14 04:26:22 (6849) [INFO] 
* 2024-07-14 04:26:29 (6879) [INFO] 
* 2024-07-14 04:26:31 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-14 04:26:31 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-14 04:26:31 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-14 04:26:33 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-14 04:26:33 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-14 04:26:33 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-14 04:26:33 (6849) [INFO] 
* 2024-07-14 04:26:34 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-14 04:26:34 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-14 04:26:34 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-14 04:26:34 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-14 04:26:34 (6862) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-14 04:26:34 (6862) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-14 04:26:34 (6862) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-14 04:26:34 (6862) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-14 04:26:34 (6862) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-14 04:26:34 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-14 04:26:34 (6862) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-14 04:26:34 (6879) [INFO] 
* 2024-07-14 04:26: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-14 04:26:41 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-14 04:26:41 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-14 04:26:42 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cI4BbRh4k6/ea_profile.json
* 2024-07-14 04:26:44 (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/cI4BbRh4k6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-14 04:26:44 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-15 04:25:40 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-15 04:25:41 (8150) [INFO] Script is up to date.
* 2024-07-15 04:25:43 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-15 04:25:43 (6849) [INFO] 
* 2024-07-15 04:25:47 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:47 (6879) [INFO] 
* 2024-07-15 04:25:47 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-15 04:25:48 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-15 04:25:48 (6849) [INFO] 
* 2024-07-15 04:25:58 (6879) [INFO] 
* 2024-07-15 04:25:59 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-15 04:25:59 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-15 04:25:59 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-15 04:26:01 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-15 04:26:01 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-15 04:26:01 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-15 04:26:01 (6849) [INFO] 
* 2024-07-15 04:26:01 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-15 04:26:02 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-15 04:26:02 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-15 04:26:02 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-15 04:26:02 (6862) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-15 04:26:02 (6862) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-15 04:26:02 (6862) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-15 04:26:02 (6862) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-15 04:26:02 (6862) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-15 04:26:02 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-15 04:26:02 (6862) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-15 04:26:02 (6879) [INFO] 
* 2024-07-15 04:26: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-15 04:26:11 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-15 04:26:11 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-15 04:26:12 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vnb8H0EvXN/ea_profile.json
* 2024-07-15 04:26:14 (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/vnb8H0EvXN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-15 04:26:14 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-16 04:25:47 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-16 04:25:47 (8150) [INFO] Script is up to date.
* 2024-07-16 04:25:49 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-16 04:25:49 (6849) [INFO] 
* 2024-07-16 04:25:58 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:58 (6879) [INFO] 
* 2024-07-16 04:25:58 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-16 04:25:59 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-16 04:25:59 (6849) [INFO] 
* 2024-07-16 04:26:04 (6879) [INFO] 
* 2024-07-16 04:26:06 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-16 04:26:06 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-16 04:26:06 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-16 04:26:08 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-16 04:26:08 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-16 04:26:08 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-16 04:26:08 (6849) [INFO] 
* 2024-07-16 04:26:08 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-16 04:26:08 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-16 04:26:08 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-16 04:26:08 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-16 04:26:08 (6862) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-16 04:26:08 (6862) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-16 04:26:08 (6862) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-16 04:26:08 (6862) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-16 04:26:08 (6862) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-16 04:26:08 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-16 04:26:08 (6862) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-16 04:26:08 (6879) [INFO] 
* 2024-07-16 04:26:12 (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 04:26:12 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-16 04:26:13 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-16 04:26:13 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OUyjyvs0Wd/ea_profile.json
* 2024-07-16 04:26:15 (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/OUyjyvs0Wd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-16 04:26:15 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-17 04:25:37 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-17 04:25:37 (8133) [INFO] Newer version of script found. Downloading.
* 2024-07-17 04:25:38 (8142) [INFO] Script update to version 48 successful.
* 2024-07-17 04:25:40 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-17 04:25:40 (6847) [INFO] 
* 2024-07-17 04:25:44 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:44 (6877) [INFO] 
* 2024-07-17 04:25:44 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-17 04:25:45 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-17 04:25:45 (6847) [INFO] 
* 2024-07-17 04:25:55 (6877) [INFO] 
* 2024-07-17 04:25:57 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-17 04:25:57 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-17 04:25:57 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-17 04:25:59 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-17 04:25:59 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-17 04:25:59 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-17 04:25:59 (6847) [INFO] 
* 2024-07-17 04:25:59 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-17 04:26:00 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-17 04:26:00 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-17 04:26:00 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-17 04:26:00 (6860) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-17 04:26:00 (6860) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-17 04:26:00 (6860) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-17 04:26:00 (6860) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-17 04:26:00 (6860) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-17 04:26:00 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-17 04:26:00 (6860) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-17 04:26:00 (6877) [INFO] 
* 2024-07-17 04:26: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 04:26:06 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-17 04:26:06 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-17 04:26:07 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lZREoCXVM3/ea_profile.json
* 2024-07-17 04:26:09 (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/lZREoCXVM3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-17 04:26:09 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-18 04:25:37 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-18 04:25:37 (8148) [INFO] Script is up to date.
* 2024-07-18 04:25:39 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-18 04:25:39 (6847) [INFO] 
* 2024-07-18 04:25:43 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:43 (6877) [INFO] 
* 2024-07-18 04:25:43 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-18 04:25:44 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-18 04:25:44 (6847) [INFO] 
* 2024-07-18 04:25:53 (6877) [INFO] 
* 2024-07-18 04:25:54 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-18 04:25:54 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-18 04:25:54 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-18 04:25:56 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-18 04:25:56 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-18 04:25:56 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-18 04:25:56 (6847) [INFO] 
* 2024-07-18 04:25:56 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-18 04:25:57 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-18 04:25:57 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-18 04:25:57 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-18 04:25:57 (6860) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-18 04:25:57 (6860) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-18 04:25:57 (6860) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-18 04:25:57 (6860) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-18 04:25:57 (6860) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-18 04:25:57 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-18 04:25:57 (6860) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-18 04:25:57 (6877) [INFO] 
* 2024-07-18 04:26:04 (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 04:26:04 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-18 04:26:04 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-18 04:26:05 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3otk5lPly_/ea_profile.json
* 2024-07-18 04:26:07 (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/3otk5lPly_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-18 04:26:07 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-19 04:25:35 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-19 04:25:35 (8148) [INFO] Script is up to date.
* 2024-07-19 04:25:37 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-19 04:25:37 (6847) [INFO] 
* 2024-07-19 04:25:41 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:41 (6877) [INFO] 
* 2024-07-19 04:25:41 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-19 04:25:42 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-19 04:25:42 (6847) [INFO] 
* 2024-07-19 04:25:48 (6877) [INFO] 
* 2024-07-19 04:25:50 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-19 04:25:50 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-19 04:25:50 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-19 04:25:53 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-19 04:25:53 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-19 04:25:53 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-19 04:25:53 (6847) [INFO] 
* 2024-07-19 04:25:53 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-19 04:25:54 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-19 04:25:54 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-19 04:25:54 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-19 04:25:54 (6860) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-19 04:25:54 (6860) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-19 04:25:54 (6860) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-19 04:25:54 (6860) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-19 04:25:54 (6860) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-19 04:25:54 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-19 04:25:54 (6860) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-19 04:25:54 (6877) [INFO] 
* 2024-07-19 04:25:59 (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 04:25:59 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-19 04:25:59 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-19 04:26:00 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zPptDvyHlo/ea_profile.json
* 2024-07-19 04:26:02 (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/zPptDvyHlo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-19 04:26:02 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-20 04:26:28 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-20 04:26:28 (8148) [INFO] Script is up to date.
* 2024-07-20 04:26:30 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-20 04:26:30 (6847) [INFO] 
* 2024-07-20 04:26:34 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:34 (6877) [INFO] 
* 2024-07-20 04:26:34 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-20 04:26:34 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-20 04:26:34 (6847) [INFO] 
* 2024-07-20 04:26:41 (6877) [INFO] 
* 2024-07-20 04:26:42 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-20 04:26:42 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-20 04:26:42 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-20 04:26:44 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-20 04:26:44 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-20 04:26:44 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-20 04:26:44 (6847) [INFO] 
* 2024-07-20 04:26:44 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-20 04:26:44 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-20 04:26:44 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-20 04:26:44 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-20 04:26:44 (6860) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-20 04:26:44 (6860) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-20 04:26:44 (6860) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-20 04:26:44 (6860) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-20 04:26:44 (6860) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-20 04:26:44 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-20 04:26:44 (6860) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-20 04:26:44 (6877) [INFO] 
* 2024-07-20 04:26:50 (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 04:26:50 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-20 04:26:51 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-20 04:26:52 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mY_suz0Fjx/ea_profile.json
* 2024-07-20 04:26:53 (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/mY_suz0Fjx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-20 04:26:53 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-21 04:26:23 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-21 04:26:23 (8148) [INFO] Script is up to date.
* 2024-07-21 04:26:24 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-21 04:26:24 (6847) [INFO] 
* 2024-07-21 04:26:27 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:27 (6877) [INFO] 
* 2024-07-21 04:26:27 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-21 04:26:28 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-21 04:26:28 (6847) [INFO] 
* 2024-07-21 04:26:32 (6877) [INFO] 
* 2024-07-21 04:26:34 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-21 04:26:34 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-21 04:26:34 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-21 04:26:36 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-21 04:26:36 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-21 04:26:36 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-21 04:26:36 (6847) [INFO] 
* 2024-07-21 04:26:36 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-21 04:26:36 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-21 04:26:36 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-21 04:26:36 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-21 04:26:36 (6860) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-21 04:26:36 (6860) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-21 04:26:36 (6860) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-21 04:26:36 (6860) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-21 04:26:36 (6860) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-21 04:26:36 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-21 04:26:36 (6860) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-21 04:26:36 (6877) [INFO] 
* 2024-07-21 04:26: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-21 04:26:42 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-21 04:26:43 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-21 04:26:43 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Q0iEiodUjQ/ea_profile.json
* 2024-07-21 04:26:45 (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/Q0iEiodUjQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-21 04:26:45 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-22 04:25:36 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-22 04:25:36 (8148) [INFO] Script is up to date.
* 2024-07-22 04:25:38 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-22 04:25:38 (6847) [INFO] 
* 2024-07-22 04:25:42 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:42 (6877) [INFO] 
* 2024-07-22 04:25:42 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-22 04:25:42 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-22 04:25:42 (6847) [INFO] 
* 2024-07-22 04:25:48 (6877) [INFO] 
* 2024-07-22 04:25:49 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-22 04:25:49 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-22 04:25:49 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-22 04:25:52 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-22 04:25:52 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-22 04:25:52 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-22 04:25:52 (6847) [INFO] 
* 2024-07-22 04:25:52 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-22 04:25:52 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-22 04:25:52 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-22 04:25:52 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-22 04:25:52 (6860) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-22 04:25:52 (6860) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-22 04:25:52 (6860) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-22 04:25:52 (6860) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-22 04:25:52 (6860) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-22 04:25:52 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-22 04:25:52 (6860) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-22 04:25:52 (6877) [INFO] 
* 2024-07-22 04:25:58 (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 04:25:58 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-22 04:25:58 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-22 04:25:59 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9lUeOwo1LO/ea_profile.json
* 2024-07-22 04:26:01 (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/9lUeOwo1LO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-22 04:26:01 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-23 04:25:36 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-23 04:25:36 (8148) [INFO] Script is up to date.
* 2024-07-23 04:25:38 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-23 04:25:38 (6847) [INFO] 
* 2024-07-23 04:25:39 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:40 (6877) [INFO] 
* 2024-07-23 04:25:40 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-23 04:25:40 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-23 04:25:40 (6847) [INFO] 
* 2024-07-23 04:25:46 (6877) [INFO] 
* 2024-07-23 04:25:47 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-23 04:25:47 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-23 04:25:47 (2163) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-23 04:25:50 (2025) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-23 04:25:50 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-23 04:25:50 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-23 04:25:50 (6847) [INFO] 
* 2024-07-23 04:25:50 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-23 04:25:50 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-23 04:25:50 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-23 04:25:50 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-23 04:25:50 (6860) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-23 04:25:50 (6860) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-23 04:25:50 (6860) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-23 04:25:50 (6860) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-23 04:25:50 (6860) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-23 04:25:50 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-23 04:25:50 (6860) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-23 04:25:50 (6877) [INFO] 
* 2024-07-23 04:25:55 (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 04:25:55 (2036) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-23 04:25:56 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-23 04:25:56 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AU1Ogu5yG3/ea_profile.json
* 2024-07-23 04:25:58 (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/AU1Ogu5yG3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-23 04:25:58 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-24 04:25:43 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-24 04:25:43 (8131) [INFO] Newer version of script found. Downloading.
* 2024-07-24 04:25:44 (8140) [INFO] Script update to version 49 successful.
* 2024-07-24 04:25:45 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-24 04:25:45 (6908) [INFO] 
* 2024-07-24 04:25:48 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:48 (6938) [INFO] 
* 2024-07-24 04:25:48 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-24 04:25:49 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-24 04:25:49 (6908) [INFO] 
* 2024-07-24 04:25:51 (6938) [INFO] 
* 2024-07-24 04:25:52 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-24 04:25:52 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-24 04:25:52 (2188) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-24 04:25:54 (2047) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-24 04:25:54 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-24 04:25:54 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-24 04:25:54 (6908) [INFO] 
* 2024-07-24 04:25:54 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-24 04:25:54 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-24 04:25:54 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-24 04:25:54 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-24 04:25:54 (6921) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-24 04:25:54 (6921) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-24 04:25:54 (6921) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-24 04:25:54 (6921) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-24 04:25:54 (6921) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-24 04:25:54 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-24 04:25:54 (6921) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-24 04:25:54 (6938) [INFO] 
* 2024-07-24 04:26:01 (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 04:26:01 (2058) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-24 04:26:02 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-24 04:26:03 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vom9Bylbo0/ea_profile.json
* 2024-07-24 04:26:04 (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/vom9Bylbo0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-24 04:26:04 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-25 04:25:35 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-25 04:25:36 (8209) [INFO] Script is up to date.
* 2024-07-25 04:25:38 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-25 04:25:38 (6908) [INFO] 
* 2024-07-25 04:25:41 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:41 (6938) [INFO] 
* 2024-07-25 04:25:42 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-25 04:25:42 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-25 04:25:42 (6908) [INFO] 
* 2024-07-25 04:25:48 (6938) [INFO] 
* 2024-07-25 04:25:50 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-25 04:25:50 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-25 04:25:50 (2188) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-25 04:25:52 (2047) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-25 04:25:52 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-25 04:25:52 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-25 04:25:52 (6908) [INFO] 
* 2024-07-25 04:25:52 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-25 04:25:52 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-25 04:25:52 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-25 04:25:52 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-25 04:25:52 (6921) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-25 04:25:52 (6921) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-25 04:25:52 (6921) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-25 04:25:52 (6921) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-25 04:25:52 (6921) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-25 04:25:52 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-25 04:25:52 (6921) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-25 04:25:52 (6938) [INFO] 
* 2024-07-25 04:25: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-25 04:25:58 (2058) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-25 04:25:58 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-25 04:25:59 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6O42WlxwMv/ea_profile.json
* 2024-07-25 04:26:01 (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/6O42WlxwMv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-25 04:26:01 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-26 04:26:00 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-26 04:26:00 (8209) [INFO] Script is up to date.
* 2024-07-26 04:26:03 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-26 04:26:03 (6908) [INFO] 
* 2024-07-26 04:26:06 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:26:06 (6938) [INFO] 
* 2024-07-26 04:26:06 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-26 04:26:07 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-26 04:26:07 (6908) [INFO] 
* 2024-07-26 04:26:11 (6938) [INFO] 
* 2024-07-26 04:26:12 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-26 04:26:12 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-26 04:26:12 (2188) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-26 04:26:18 (2047) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-26 04:26:18 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-26 04:26:18 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-26 04:26:18 (6908) [INFO] 
* 2024-07-26 04:26:18 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-26 04:26:19 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-26 04:26:19 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-26 04:26:19 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-26 04:26:19 (6921) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-26 04:26:19 (6921) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-26 04:26:19 (6921) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-26 04:26:19 (6921) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-26 04:26:19 (6921) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-26 04:26:19 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-26 04:26:19 (6921) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-26 04:26:19 (6938) [INFO] 
* 2024-07-26 04:26:34 (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 04:26:34 (2058) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-26 04:26:34 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-26 04:26:35 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yAhiTgjsbL/ea_profile.json
* 2024-07-26 04:26: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/yAhiTgjsbL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-26 04:26:42 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-27 04:26:24 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-27 04:26:24 (8209) [INFO] Script is up to date.
* 2024-07-27 04:26:26 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-27 04:26:26 (6908) [INFO] 
* 2024-07-27 04:26:30 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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-27 04:26:30 (6938) [INFO] 
* 2024-07-27 04:26:31 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-27 04:26:31 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-27 04:26:31 (6908) [INFO] 
* 2024-07-27 04:26:37 (6938) [INFO] 
* 2024-07-27 04:26:39 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-27 04:26:39 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-27 04:26:39 (2188) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-27 04:26:42 (2047) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-27 04:26:42 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-27 04:26:42 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-27 04:26:42 (6908) [INFO] 
* 2024-07-27 04:26:42 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-27 04:26:42 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-27 04:26:42 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-27 04:26:42 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-27 04:26:42 (6921) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-27 04:26:42 (6921) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-27 04:26:42 (6921) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-27 04:26:42 (6921) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-27 04:26:42 (6921) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-27 04:26:42 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-27 04:26:42 (6921) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-27 04:26:42 (6938) [INFO] 
* 2024-07-27 04:26: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-27 04:26:50 (2058) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-27 04:26:50 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-27 04:26:51 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/moc0D4eXGo/ea_profile.json
* 2024-07-27 04:26:53 (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/moc0D4eXGo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-27 04:26:53 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-28 04:26:31 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-28 04:26:31 (8209) [INFO] Script is up to date.
* 2024-07-28 04:26:33 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-28 04:26:33 (6908) [INFO] 
* 2024-07-28 04:26:37 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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-28 04:26:37 (6938) [INFO] 
* 2024-07-28 04:26:37 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-28 04:26:37 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-28 04:26:37 (6908) [INFO] 
* 2024-07-28 04:26:43 (6938) [INFO] 
* 2024-07-28 04:26:44 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-28 04:26:44 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-28 04:26:44 (2188) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-28 04:26:47 (2047) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-28 04:26:47 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-28 04:26:47 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-28 04:26:47 (6908) [INFO] 
* 2024-07-28 04:26:47 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-28 04:26:47 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-28 04:26:47 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-28 04:26:47 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-28 04:26:47 (6921) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-28 04:26:47 (6921) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-28 04:26:47 (6921) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-28 04:26:47 (6921) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-28 04:26:47 (6921) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-28 04:26:47 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-28 04:26:47 (6921) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-28 04:26:47 (6938) [INFO] 
* 2024-07-28 04:26:52 (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-28 04:26:52 (2058) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-28 04:26:53 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-28 04:26:54 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AyilRQAFCv/ea_profile.json
* 2024-07-28 04:26: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/AyilRQAFCv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-28 04:26:56 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-29 04:25:30 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-29 04:25:30 (8209) [INFO] Script is up to date.
* 2024-07-29 04:25:31 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-29 04:25:31 (6908) [INFO] 
* 2024-07-29 04:25:33 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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-29 04:25:33 (6938) [INFO] 
* 2024-07-29 04:25:34 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-29 04:25:34 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-29 04:25:34 (6908) [INFO] 
* 2024-07-29 04:25:39 (6938) [INFO] 
* 2024-07-29 04:25:41 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-29 04:25:41 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-29 04:25:41 (2188) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-29 04:25:43 (2047) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-29 04:25:43 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-29 04:25:43 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-29 04:25:43 (6908) [INFO] 
* 2024-07-29 04:25:43 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-29 04:25:44 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-29 04:25:44 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-29 04:25:44 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-29 04:25:44 (6921) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-29 04:25:44 (6921) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-29 04:25:44 (6921) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-29 04:25:44 (6921) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-29 04:25:44 (6921) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-29 04:25:44 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-29 04:25:44 (6921) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-29 04:25:44 (6938) [INFO] 
* 2024-07-29 04:25:51 (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-29 04:25:51 (2058) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-29 04:25:51 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-29 04:25:52 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8JMX6mYojy/ea_profile.json
* 2024-07-29 04:25:54 (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/8JMX6mYojy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-29 04:25:54 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-30 04:25:35 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-30 04:25:35 (8209) [INFO] Script is up to date.
* 2024-07-30 04:25:36 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-30 04:25:36 (6908) [INFO] 
* 2024-07-30 04:25:38 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:38 (6938) [INFO] 
* 2024-07-30 04:25:39 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-30 04:25:39 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-30 04:25:39 (6908) [INFO] 
* 2024-07-30 04:25:44 (6938) [INFO] 
* 2024-07-30 04:25:46 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-30 04:25:46 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-30 04:25:46 (2188) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-30 04:25:48 (2047) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-30 04:25:48 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-30 04:25:48 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-30 04:25:48 (6908) [INFO] 
* 2024-07-30 04:25:48 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-30 04:25:48 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-30 04:25:48 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-30 04:25:48 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-30 04:25:48 (6921) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-30 04:25:48 (6921) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-30 04:25:48 (6921) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-30 04:25:48 (6921) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-30 04:25:48 (6921) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-30 04:25:48 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-30 04:25:48 (6921) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-30 04:25:48 (6938) [INFO] 
* 2024-07-30 04:25:53 (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 04:25:53 (2058) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-30 04:25:53 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-30 04:25:54 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Yg52yuqeIQ/ea_profile.json
* 2024-07-30 04:25: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/Yg52yuqeIQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-30 04:25:56 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-31 04:25:31 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-31 04:25:31 (8209) [INFO] Script is up to date.
* 2024-07-31 04:25:33 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-31 04:25:33 (6908) [INFO] 
* 2024-07-31 04:25:36 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:36 (6938) [INFO] 
* 2024-07-31 04:25:36 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-07-31 04:25:37 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-31 04:25:37 (6908) [INFO] 
* 2024-07-31 04:25:43 (6938) [INFO] 
* 2024-07-31 04:25:45 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-07-31 04:25:45 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-07-31 04:25:45 (2188) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-07-31 04:25:47 (2047) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-31 04:25:47 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-31 04:25:47 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-31 04:25:47 (6908) [INFO] 
* 2024-07-31 04:25:47 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-31 04:25:47 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-31 04:25:47 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-31 04:25:47 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-31 04:25:47 (6921) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-07-31 04:25:47 (6921) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-31 04:25:47 (6921) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-31 04:25:47 (6921) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-07-31 04:25:47 (6921) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-07-31 04:25:47 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-31 04:25:47 (6921) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-07-31 04:25:47 (6938) [INFO] 
* 2024-07-31 04:25:51 (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 04:25:51 (2058) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-31 04:25:51 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-31 04:25:52 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rHXOLI3rwV/ea_profile.json
* 2024-07-31 04:25:54 (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/rHXOLI3rwV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-31 04:25:54 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-01 04:25:31 (8187) [INFO] Self-update of script version 49 requested.
* 2024-08-01 04:25:31 (8209) [INFO] Script is up to date.
* 2024-08-01 04:25:34 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-01 04:25:34 (6908) [INFO] 
* 2024-08-01 04:25:37 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 1, "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 04:25:37 (6938) [INFO] 
* 2024-08-01 04:25:37 (625) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-01 04:25:38 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-08-01 04:25:38 (6908) [INFO] 
* 2024-08-01 04:25:43 (6938) [INFO] 
* 2024-08-01 04:25:44 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-01 04:25:44 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-01 04:25:44 (2188) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-01 04:25:46 (2047) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-01 04:25:46 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-01 04:25:46 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-08-01 04:25:46 (6908) [INFO] 
* 2024-08-01 04:25:46 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-01 04:25:47 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-01 04:25:47 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-01 04:25:47 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-01 04:25:47 (6921) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-01 04:25:47 (6921) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-01 04:25:47 (6921) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-01 04:25:47 (6921) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-01 04:25:47 (6921) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-01 04:25:47 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-08-01 04:25:47 (6921) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-01 04:25:47 (6938) [INFO] 
* 2024-08-01 04:25:53 (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 04:25:53 (2058) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-01 04:25:53 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-01 04:25:54 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qYItqsXMjy/ea_profile.json
* 2024-08-01 04:25:57 (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/qYItqsXMjy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-08-01 04:25:57 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-02 04:25:37 (8187) [INFO] Self-update of script version 49 requested.
* 2024-08-02 04:25:37 (8192) [INFO] Newer version of script found. Downloading.
* 2024-08-02 04:25:38 (8201) [INFO] Script update to version 50 successful.
* 2024-08-02 04:25:39 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-02 04:25:39 (7164) [INFO] 
* 2024-08-02 04:25:42 (637) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-02 04:25:43 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-02 04:25:43 (7164) [INFO] 
* 2024-08-02 04:25:50 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-02 04:25:50 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-02 04:25:50 (2200) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-02 04:25:53 (2059) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-02 04:25:53 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-02 04:25:53 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-02 04:25:53 (7164) [INFO] 
* 2024-08-02 04:25:53 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-02 04:25:53 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-02 04:25:53 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-02 04:25:53 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-02 04:25:53 (7177) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-02 04:25:53 (7177) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-02 04:25:53 (7177) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-02 04:25:53 (7177) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-02 04:25:53 (7177) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-02 04:25:53 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-02 04:25:53 (7177) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-02 04:25:53 (7194) [INFO] 
* 2024-08-02 04:25:58 (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 04:25:58 (2070) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-02 04:25:58 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-02 04:25:59 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7WBp7ITbaC/ea_profile.json
* 2024-08-02 04:26:01 (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/7WBp7ITbaC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-02 04:26:01 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-03 04:26:28 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-03 04:26:28 (8496) [INFO] Script is up to date.
* 2024-08-03 04:26:30 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-03 04:26:30 (7164) [INFO] 
* 2024-08-03 04:26:35 (637) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-03 04:26:35 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-03 04:26:35 (7164) [INFO] 
* 2024-08-03 04:26:42 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-03 04:26:42 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-03 04:26:42 (2200) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-03 04:26:44 (2059) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-03 04:26:44 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-03 04:26:44 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-03 04:26:44 (7164) [INFO] 
* 2024-08-03 04:26:44 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-03 04:26:45 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-03 04:26:45 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-03 04:26:45 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-03 04:26:45 (7177) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-03 04:26:45 (7177) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-03 04:26:45 (7177) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-03 04:26:45 (7177) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-03 04:26:45 (7177) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-03 04:26:45 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-03 04:26:45 (7177) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-03 04:26:45 (7194) [INFO] 
* 2024-08-03 04:26:50 (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 04:26:50 (2070) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-03 04:26:51 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-03 04:26:51 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2oS95lpX5u/ea_profile.json
* 2024-08-03 04:26:54 (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/2oS95lpX5u/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-03 04:26:54 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-04 04:26:28 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-04 04:26:28 (8496) [INFO] Script is up to date.
* 2024-08-04 04:26:29 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-04 04:26:29 (7164) [INFO] 
* 2024-08-04 04:26:33 (637) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-04 04:26:33 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-04 04:26:33 (7164) [INFO] 
* 2024-08-04 04:26:40 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-04 04:26:40 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-04 04:26:40 (2200) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-04 04:26:43 (2059) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-04 04:26:43 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-04 04:26:43 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-04 04:26:43 (7164) [INFO] 
* 2024-08-04 04:26:43 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-04 04:26:43 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-04 04:26:43 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-04 04:26:43 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-04 04:26:43 (7177) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-04 04:26:43 (7177) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-04 04:26:43 (7177) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-04 04:26:43 (7177) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-04 04:26:43 (7177) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-04 04:26:43 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-04 04:26:43 (7177) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-04 04:26:43 (7194) [INFO] 
* 2024-08-04 04:26:49 (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 04:26:49 (2070) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-04 04:26:49 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-04 04:26:50 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2SNBEK6EIw/ea_profile.json
* 2024-08-04 04:26:53 (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/2SNBEK6EIw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-04 04:26:53 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-05 04:25:33 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-05 04:25:33 (8496) [INFO] Script is up to date.
* 2024-08-05 04:25:34 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-05 04:25:34 (7164) [INFO] 
* 2024-08-05 04:25:37 (637) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-05 04:25:38 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-05 04:25:38 (7164) [INFO] 
* 2024-08-05 04:25:46 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-05 04:25:46 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-05 04:25:46 (2200) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-05 04:25:48 (2059) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-05 04:25:48 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-05 04:25:48 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-05 04:25:48 (7164) [INFO] 
* 2024-08-05 04:25:49 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-05 04:25:49 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-05 04:25:49 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-05 04:25:49 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-05 04:25:49 (7177) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-05 04:25:49 (7177) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-05 04:25:49 (7177) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-05 04:25:49 (7177) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-05 04:25:49 (7177) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-05 04:25:49 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-05 04:25:49 (7177) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-05 04:25:49 (7194) [INFO] 
* 2024-08-05 04:25:54 (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 04:25:54 (2070) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-05 04:25:54 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-05 04:25:55 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6VC0xwiz0y/ea_profile.json
* 2024-08-05 04:25:57 (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/6VC0xwiz0y/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-05 04:25:57 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-06 04:25:32 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-06 04:25:32 (8496) [INFO] Script is up to date.
* 2024-08-06 04:25:35 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-06 04:25:35 (7164) [INFO] 
* 2024-08-06 04:25:39 (637) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-06 04:25:39 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-06 04:25:39 (7164) [INFO] 
* 2024-08-06 04:25:46 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-06 04:25:46 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-06 04:25:46 (2200) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-06 04:25:48 (2059) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-06 04:25:48 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-06 04:25:48 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-06 04:25:48 (7164) [INFO] 
* 2024-08-06 04:25:49 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-06 04:25:49 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-06 04:25:49 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-06 04:25:49 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-06 04:25:49 (7177) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-06 04:25:49 (7177) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-06 04:25:49 (7177) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-06 04:25:49 (7177) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-06 04:25:49 (7177) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-06 04:25:49 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-06 04:25:49 (7177) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-06 04:25:49 (7194) [INFO] 
* 2024-08-06 04:25:53 (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 04:25:53 (2070) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-06 04:25:53 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-06 04:25:54 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nDXS2Aj6Dn/ea_profile.json
* 2024-08-06 04:25: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/nDXS2Aj6Dn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-06 04:25:56 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-07 04:26:26 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-07 04:26:26 (8496) [INFO] Script is up to date.
* 2024-08-07 04:26:28 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-07 04:26:28 (7164) [INFO] 
* 2024-08-07 04:26:32 (637) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-07 04:26:33 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-07 04:26:33 (7164) [INFO] 
* 2024-08-07 04:26:39 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-07 04:26:39 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-07 04:26:39 (2200) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-07 04:26:42 (2059) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-07 04:26:42 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-07 04:26:42 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-07 04:26:42 (7164) [INFO] 
* 2024-08-07 04:26:42 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-07 04:26:42 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-07 04:26:42 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-07 04:26:42 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-07 04:26:42 (7177) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-07 04:26:42 (7177) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-07 04:26:42 (7177) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-07 04:26:42 (7177) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-07 04:26:42 (7177) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-07 04:26:42 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-07 04:26:42 (7177) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-07 04:26:42 (7194) [INFO] 
* 2024-08-07 04:26:47 (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 04:26:47 (2070) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-07 04:26:47 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-07 04:26:48 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Kh454BjXdY/ea_profile.json
* 2024-08-07 04:26:50 (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/Kh454BjXdY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-07 04:26:50 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-08 04:25:33 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-08 04:25:33 (8479) [INFO] Newer version of script found. Downloading.
* 2024-08-08 04:25:33 (8488) [INFO] Script update to version 51 successful.
* 2024-08-08 04:25:34 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-08 04:25:34 (7324) [INFO] 
* 2024-08-08 04:25:37 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-08 04:25:38 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-08 04:25:38 (7324) [INFO] 
* 2024-08-08 04:25:44 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-08 04:25:44 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-08 04:25:44 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-08 04:25:46 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-08 04:25:46 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-08 04:25:46 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-08 04:25:46 (7324) [INFO] 
* 2024-08-08 04:25:46 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-08 04:25:46 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-08 04:25:46 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-08 04:25:46 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-08 04:25:46 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-08 04:25:46 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-08 04:25:46 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-08 04:25:46 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-08 04:25:46 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-08 04:25:46 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-08 04:25:46 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-08 04:25:47 (7354) [INFO] 
* 2024-08-08 04:25:51 (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 04:25:51 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-08 04:25:51 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-08 04:25:52 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bwPLD9Q6ew/ea_profile.json
* 2024-08-08 04:25:54 (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/bwPLD9Q6ew/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-08 04:25:54 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-09 04:25:36 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-09 04:25:36 (8664) [INFO] Script is up to date.
* 2024-08-09 04:25:37 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-09 04:25:37 (7324) [INFO] 
* 2024-08-09 04:25:42 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-09 04:25:42 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-09 04:25:42 (7324) [INFO] 
* 2024-08-09 04:25:50 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-09 04:25:50 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-09 04:25:50 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-09 04:25:51 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-09 04:25:51 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-09 04:25:51 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-09 04:25:51 (7324) [INFO] 
* 2024-08-09 04:25:52 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-09 04:25:52 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-09 04:25:52 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-09 04:25:52 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-09 04:25:52 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-09 04:25:52 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-09 04:25:52 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-09 04:25:52 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-09 04:25:52 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-09 04:25:52 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-09 04:25:52 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-09 04:25:52 (7354) [INFO] 
* 2024-08-09 04:25:57 (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 04:25:57 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-09 04:25:57 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-09 04:25:58 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XroaGp6VnA/ea_profile.json
* 2024-08-09 04:25:59 (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/XroaGp6VnA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-09 04:25:59 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-10 04:26:31 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-10 04:26:31 (8664) [INFO] Script is up to date.
* 2024-08-10 04:26:32 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-10 04:26:32 (7324) [INFO] 
* 2024-08-10 04:26:36 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-10 04:26:36 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-10 04:26:36 (7324) [INFO] 
* 2024-08-10 04:26:43 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-10 04:26:43 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-10 04:26:43 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-10 04:26:44 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-10 04:26:44 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-10 04:26:44 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-10 04:26:44 (7324) [INFO] 
* 2024-08-10 04:26:44 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-10 04:26:45 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-10 04:26:45 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-10 04:26:45 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-10 04:26:45 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-10 04:26:45 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-10 04:26:45 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-10 04:26:45 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-10 04:26:45 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-10 04:26:45 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-10 04:26:45 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-10 04:26:45 (7354) [INFO] 
* 2024-08-10 04:26:49 (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 04:26:49 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-10 04:26:49 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-10 04:26:50 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/U8pq_1X4sf/ea_profile.json
* 2024-08-10 04:26:52 (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/U8pq_1X4sf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-10 04:26:52 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-11 04:26:24 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-11 04:26:24 (8664) [INFO] Script is up to date.
* 2024-08-11 04:26:25 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-11 04:26:25 (7324) [INFO] 
* 2024-08-11 04:26:28 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-11 04:26:29 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-11 04:26:29 (7324) [INFO] 
* 2024-08-11 04:26:35 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-11 04:26:35 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-11 04:26:35 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-11 04:26:38 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-11 04:26:38 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-11 04:26:38 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-11 04:26:38 (7324) [INFO] 
* 2024-08-11 04:26:38 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-11 04:26:38 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-11 04:26:38 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-11 04:26:38 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-11 04:26:38 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-11 04:26:38 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-11 04:26:38 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-11 04:26:38 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-11 04:26:38 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-11 04:26:38 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-11 04:26:38 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-11 04:26:38 (7354) [INFO] 
* 2024-08-11 04:26:43 (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 04:26:43 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-11 04:26:43 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-11 04:26:44 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ex_0D21vL5/ea_profile.json
* 2024-08-11 04:26:47 (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/Ex_0D21vL5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-11 04:26:47 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-12 04:25:39 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-12 04:25:39 (8664) [INFO] Script is up to date.
* 2024-08-12 04:25:40 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-12 04:25:40 (7324) [INFO] 
* 2024-08-12 04:25:44 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-12 04:25:44 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-12 04:25:44 (7324) [INFO] 
* 2024-08-12 04:25:51 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-12 04:25:51 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-12 04:25:51 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-12 04:25:53 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-12 04:25:53 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-12 04:25:53 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-12 04:25:53 (7324) [INFO] 
* 2024-08-12 04:25:53 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-12 04:25:53 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-12 04:25:53 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-12 04:25:53 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-12 04:25:53 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-12 04:25:53 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-12 04:25:53 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-12 04:25:53 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-12 04:25:53 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-12 04:25:53 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-12 04:25:53 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-12 04:25:53 (7354) [INFO] 
* 2024-08-12 04:25:57 (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 04:25:57 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-12 04:25:57 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-12 04:25:58 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7p1BXlCeYi/ea_profile.json
* 2024-08-12 04:26:00 (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/7p1BXlCeYi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-12 04:26:00 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-13 04:25:38 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-13 04:25:38 (8664) [INFO] Script is up to date.
* 2024-08-13 04:25:41 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-13 04:25:41 (7324) [INFO] 
* 2024-08-13 04:25:44 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-13 04:25:45 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-13 04:25:45 (7324) [INFO] 
* 2024-08-13 04:25:52 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-13 04:25:52 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-13 04:25:52 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-13 04:25:54 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-13 04:25:54 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-13 04:25:54 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-13 04:25:54 (7324) [INFO] 
* 2024-08-13 04:25:54 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-13 04:25:54 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-13 04:25:54 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-13 04:25:54 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-13 04:25:54 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-13 04:25:54 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-13 04:25:54 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-13 04:25:54 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-13 04:25:54 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-13 04:25:54 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-13 04:25:54 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-13 04:25:54 (7354) [INFO] 
* 2024-08-13 04:25: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-13 04:25:59 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-13 04:25:59 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-13 04:26:00 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JVYm0mtaCC/ea_profile.json
* 2024-08-13 04:26:02 (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/JVYm0mtaCC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-13 04:26:02 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-14 04:25:38 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-14 04:25:38 (8664) [INFO] Script is up to date.
* 2024-08-14 04:25:39 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-14 04:25:39 (7324) [INFO] 
* 2024-08-14 04:25:42 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-14 04:25:43 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-14 04:25:43 (7324) [INFO] 
* 2024-08-14 04:25:50 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-14 04:25:50 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-14 04:25:50 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-14 04:25:53 (2029) [WARN] Initial run of "yum makecache" failed: http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

http://63.247.64.58/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
http://63.247.64.58/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-14 04:25:53 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-14 04:25:53 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-14 04:25:53 (7324) [INFO] 
* 2024-08-14 04:25:53 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-14 04:25:53 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-14 04:25:53 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-14 04:25:53 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-14 04:25:53 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-14 04:25:53 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-14 04:25:53 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-14 04:25:53 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-14 04:25:53 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-14 04:25:53 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-14 04:25:53 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-14 04:25:53 (7354) [INFO] 
* 2024-08-14 04:25: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 04:25:59 (2040) [ERROR] http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

http://63.247.64.58/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
http://63.247.64.58/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-14 04:26:00 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-14 04:26:01 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uxX6wXOv_c/ea_profile.json
* 2024-08-14 04:26:04 (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/uxX6wXOv_c/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-14 04:26:04 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-15 04:26:19 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-15 04:26:19 (8664) [INFO] Script is up to date.
* 2024-08-15 04:26:21 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-15 04:26:21 (7324) [INFO] 
* 2024-08-15 04:26:26 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-15 04:26:26 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-15 04:26:26 (7324) [INFO] 
* 2024-08-15 04:26:35 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-15 04:26:35 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-15 04:26:35 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-15 04:26:37 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-15 04:26:37 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-15 04:26:37 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-15 04:26:37 (7324) [INFO] 
* 2024-08-15 04:26:37 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-15 04:26:37 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-15 04:26:37 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-15 04:26:37 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-15 04:26:37 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-15 04:26:37 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-15 04:26:37 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-15 04:26:37 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-15 04:26:37 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-15 04:26:37 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-15 04:26:37 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-15 04:26:37 (7354) [INFO] 
* 2024-08-15 04:26:43 (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 04:26:43 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-15 04:26:43 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-15 04:26:44 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KxTO4ldh32/ea_profile.json
* 2024-08-15 04:26:46 (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/KxTO4ldh32/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-15 04:26:46 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-16 04:25:38 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-16 04:25:38 (8664) [INFO] Script is up to date.
* 2024-08-16 04:25:39 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-16 04:25:39 (7324) [INFO] 
* 2024-08-16 04:25:42 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-16 04:25:43 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-16 04:25:43 (7324) [INFO] 
* 2024-08-16 04:25:49 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-16 04:25:49 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-16 04:25:49 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-16 04:25:51 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-16 04:25:51 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-16 04:25:51 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-16 04:25:51 (7324) [INFO] 
* 2024-08-16 04:25:51 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-16 04:25:51 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-16 04:25:51 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-16 04:25:51 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-16 04:25:51 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-16 04:25:51 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-16 04:25:51 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-16 04:25:51 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-16 04:25:51 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-16 04:25:51 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-16 04:25:51 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-16 04:25:51 (7354) [INFO] 
* 2024-08-16 04:25:55 (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 04:25:55 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-16 04:25:56 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-16 04:25:56 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/m6zq6fj_h3/ea_profile.json
* 2024-08-16 04:25: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/m6zq6fj_h3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-16 04:25:58 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-17 04:26:29 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-17 04:26:29 (8664) [INFO] Script is up to date.
* 2024-08-17 04:26:30 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-17 04:26:30 (7324) [INFO] 
* 2024-08-17 04:26:33 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-17 04:26:34 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-17 04:26:34 (7324) [INFO] 
* 2024-08-17 04:26:40 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-17 04:26:40 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-17 04:26:40 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-17 04:26:41 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-17 04:26:41 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-17 04:26:41 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-17 04:26:41 (7324) [INFO] 
* 2024-08-17 04:26:42 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-17 04:26:42 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-17 04:26:42 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-17 04:26:42 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-17 04:26:42 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-17 04:26:42 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-17 04:26:42 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-17 04:26:42 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-17 04:26:42 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-17 04:26:42 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-17 04:26:42 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-17 04:26:42 (7354) [INFO] 
* 2024-08-17 04:26:46 (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 04:26:46 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-17 04:26:46 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-17 04:26:47 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/05f5q9Us4j/ea_profile.json
* 2024-08-17 04:26: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/05f5q9Us4j/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-17 04:26:49 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-18 04:26:24 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-18 04:26:24 (8664) [INFO] Script is up to date.
* 2024-08-18 04:26:27 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-18 04:26:27 (7324) [INFO] 
* 2024-08-18 04:26:31 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-18 04:26:31 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-18 04:26:31 (7324) [INFO] 
* 2024-08-18 04:26:38 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-18 04:26:38 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-18 04:26:38 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-18 04:26:41 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-18 04:26:41 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-18 04:26:41 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-18 04:26:41 (7324) [INFO] 
* 2024-08-18 04:26:42 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-18 04:26:42 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-18 04:26:42 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-18 04:26:42 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-18 04:26:42 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-18 04:26:42 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-18 04:26:42 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-18 04:26:42 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-18 04:26:42 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-18 04:26:42 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-18 04:26:42 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-18 04:26:42 (7354) [INFO] 
* 2024-08-18 04:26: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-18 04:26:47 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-18 04:26:47 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-18 04:26:48 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gf2yuLR4rS/ea_profile.json
* 2024-08-18 04:26:51 (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/gf2yuLR4rS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-18 04:26:51 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-19 04:25:37 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-19 04:25:37 (8664) [INFO] Script is up to date.
* 2024-08-19 04:25:38 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-19 04:25:38 (7324) [INFO] 
* 2024-08-19 04:25:42 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-19 04:25:42 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-19 04:25:42 (7324) [INFO] 
* 2024-08-19 04:25:47 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-19 04:25:47 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-19 04:25:47 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-19 04:25:49 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-19 04:25:49 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-19 04:25:49 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-19 04:25:49 (7324) [INFO] 
* 2024-08-19 04:25:49 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-19 04:25:49 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-19 04:25:49 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-19 04:25:49 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-19 04:25:49 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-19 04:25:49 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-19 04:25:49 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-19 04:25:49 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-19 04:25:49 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-19 04:25:49 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-19 04:25:49 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-19 04:25:49 (7354) [INFO] 
* 2024-08-19 04:25:53 (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 04:25:53 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-19 04:25:53 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-19 04:25:54 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RdoNSByB1L/ea_profile.json
* 2024-08-19 04:25: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/RdoNSByB1L/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-19 04:25:56 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-20 04:25:36 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-20 04:25:37 (8664) [INFO] Script is up to date.
* 2024-08-20 04:25:39 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-20 04:25:39 (7324) [INFO] 
* 2024-08-20 04:25:42 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-20 04:25:42 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-20 04:25:42 (7324) [INFO] 
* 2024-08-20 04:25:49 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-20 04:25:49 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-20 04:25:49 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-20 04:25:51 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-20 04:25:51 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-20 04:25:51 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-20 04:25:51 (7324) [INFO] 
* 2024-08-20 04:25:52 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-20 04:25:52 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-20 04:25:52 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-20 04:25:52 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-20 04:25:52 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-20 04:25:52 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-20 04:25:52 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-20 04:25:52 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-20 04:25:52 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-20 04:25:52 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-20 04:25:52 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-20 04:25:52 (7354) [INFO] 
* 2024-08-20 04:25:57 (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 04:25:57 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-20 04:25:57 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-20 04:25:58 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/58PtpWGTU7/ea_profile.json
* 2024-08-20 04:26:00 (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/58PtpWGTU7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-20 04:26:00 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-21 04:25:33 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-21 04:25:33 (8664) [INFO] Script is up to date.
* 2024-08-21 04:25:34 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-21 04:25:34 (7324) [INFO] 
* 2024-08-21 04:25:39 (635) [WARN] You have postgresql-server version 9.2 installed. This will be upgraded irreversibly to version 10.0 when you switch to AlmaLinux 8
* 2024-08-21 04:25:39 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-21 04:25:39 (7324) [INFO] 
* 2024-08-21 04:25:47 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-21 04:25:47 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-21 04:25:47 (2170) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-21 04:25:49 (2029) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-21 04:25:49 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-21 04:25:49 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-21 04:25:49 (7324) [INFO] 
* 2024-08-21 04:25:49 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-21 04:25:49 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-21 04:25:49 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-21 04:25:49 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-21 04:25:49 (7337) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-21 04:25:49 (7337) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-21 04:25:49 (7337) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-21 04:25:49 (7337) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-21 04:25:49 (7337) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-21 04:25:49 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-21 04:25:49 (7337) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-21 04:25:49 (7354) [INFO] 
* 2024-08-21 04:25:53 (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 04:25:53 (2040) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-21 04:25:53 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-21 04:25:54 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MB7lsv92c4/ea_profile.json
* 2024-08-21 04:25: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/MB7lsv92c4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-21 04:25:56 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-22 04:25:37 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-22 04:25:37 (8647) [INFO] Newer version of script found. Downloading.
* 2024-08-22 04:25:39 (8656) [INFO] Script update to version 52 successful.
* 2024-08-22 04:25:40 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-22 04:25:40 (7574) [INFO] 
* 2024-08-22 04:25:44 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-22 04:25:44 (7574) [INFO] 
* 2024-08-22 04:25:52 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-22 04:25:52 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-22 04:25:52 (2104) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-22 04:25:55 (1963) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-22 04:25:55 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-22 04:25:55 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-22 04:25:55 (7574) [INFO] 
* 2024-08-22 04:25:55 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-22 04:25:55 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-22 04:25:55 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-22 04:25:55 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-22 04:25:55 (7587) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-22 04:25:55 (7587) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-22 04:25:55 (7587) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-22 04:25:55 (7587) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-22 04:25:55 (7587) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-22 04:25:55 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-22 04:25:55 (7587) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-22 04:25:55 (7604) [INFO] 
* 2024-08-22 04:26:01 (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-22 04:26:01 (1974) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-22 04:26:01 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-22 04:26:02 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZfnikCLNj6/ea_profile.json
* 2024-08-22 04:26: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/ZfnikCLNj6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-22 04:26:05 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-23 04:25:34 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-23 04:25:35 (8939) [INFO] Script is up to date.
* 2024-08-23 04:25:36 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-23 04:25:36 (7574) [INFO] 
* 2024-08-23 04:25:38 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-23 04:25:38 (7574) [INFO] 
* 2024-08-23 04:25:46 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-23 04:25:46 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-23 04:25:46 (2104) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-23 04:25:49 (1963) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-23 04:25:49 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-23 04:25:49 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-23 04:25:49 (7574) [INFO] 
* 2024-08-23 04:25:49 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-23 04:25:49 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-23 04:25:49 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-23 04:25:49 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-23 04:25:49 (7587) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-23 04:25:49 (7587) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-23 04:25:49 (7587) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-23 04:25:49 (7587) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-23 04:25:49 (7587) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-23 04:25:49 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-23 04:25:49 (7587) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-23 04:25:49 (7604) [INFO] 
* 2024-08-23 04:25:53 (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 04:25:53 (1974) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-23 04:25:54 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-23 04:25:54 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lf8Q7Dj32t/ea_profile.json
* 2024-08-23 04:25: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/lf8Q7Dj32t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-23 04:25:56 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-24 04:26:30 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-24 04:26:30 (8939) [INFO] Script is up to date.
* 2024-08-24 04:26:31 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-24 04:26:31 (7574) [INFO] 
* 2024-08-24 04:26:35 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-24 04:26:35 (7574) [INFO] 
* 2024-08-24 04:26:42 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-24 04:26:42 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-24 04:26:42 (2104) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-24 04:26:44 (1963) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-24 04:26:44 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-24 04:26:44 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-24 04:26:44 (7574) [INFO] 
* 2024-08-24 04:26:44 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-24 04:26:44 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-24 04:26:44 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-24 04:26:44 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-24 04:26:44 (7587) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-24 04:26:44 (7587) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-24 04:26:44 (7587) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-24 04:26:44 (7587) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-24 04:26:44 (7587) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-24 04:26:44 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-24 04:26:44 (7587) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-24 04:26:44 (7604) [INFO] 
* 2024-08-24 04:26:49 (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 04:26:49 (1974) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-24 04:26:49 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-24 04:26:50 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lgZZOb_Iz7/ea_profile.json
* 2024-08-24 04:26:52 (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/lgZZOb_Iz7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-24 04:26:52 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-25 04:26:26 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-25 04:26:26 (8939) [INFO] Script is up to date.
* 2024-08-25 04:26:29 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-25 04:26:29 (7574) [INFO] 
* 2024-08-25 04:26:32 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-25 04:26:32 (7574) [INFO] 
* 2024-08-25 04:26:41 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-25 04:26:41 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-25 04:26:41 (2104) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-25 04:26:43 (1963) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-25 04:26:43 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-25 04:26:43 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-25 04:26:43 (7574) [INFO] 
* 2024-08-25 04:26:44 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-25 04:26:44 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-25 04:26:44 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-25 04:26:44 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-25 04:26:44 (7587) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-25 04:26:44 (7587) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-25 04:26:44 (7587) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-25 04:26:44 (7587) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-25 04:26:44 (7587) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-25 04:26:44 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-25 04:26:44 (7587) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-25 04:26:44 (7604) [INFO] 
* 2024-08-25 04:26:49 (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 04:26:49 (1974) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-25 04:26:49 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-25 04:26:50 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kzktlGtxHw/ea_profile.json
* 2024-08-25 04:26:52 (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/kzktlGtxHw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-25 04:26:52 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-26 04:25:32 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-26 04:25:32 (8939) [INFO] Script is up to date.
* 2024-08-26 04:25:34 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-26 04:25:34 (7574) [INFO] 
* 2024-08-26 04:25:38 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-26 04:25:38 (7574) [INFO] 
* 2024-08-26 04:25:45 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-26 04:25:45 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-26 04:25:45 (2104) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-26 04:25:48 (1963) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-26 04:25:48 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-26 04:25:48 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-26 04:25:48 (7574) [INFO] 
* 2024-08-26 04:25:48 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-26 04:25:48 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-26 04:25:48 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-26 04:25:48 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-26 04:25:48 (7587) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-26 04:25:48 (7587) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-26 04:25:48 (7587) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-26 04:25:48 (7587) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-26 04:25:48 (7587) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-26 04:25:48 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-26 04:25:48 (7587) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-26 04:25:48 (7604) [INFO] 
* 2024-08-26 04:25:53 (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 04:25:53 (1974) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-26 04:25:53 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-26 04:25:54 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JQWW44UmLk/ea_profile.json
* 2024-08-26 04:25: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/JQWW44UmLk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-26 04:25:57 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-27 04:25:40 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-27 04:25:41 (8939) [INFO] Script is up to date.
* 2024-08-27 04:25:42 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-27 04:25:42 (7574) [INFO] 
* 2024-08-27 04:25:44 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-27 04:25:44 (7574) [INFO] 
* 2024-08-27 04:25:52 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-27 04:25:52 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-27 04:25:52 (2104) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-27 04:25:55 (1963) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-27 04:25:55 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-27 04:25:55 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-27 04:25:55 (7574) [INFO] 
* 2024-08-27 04:25:55 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-27 04:25:55 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-27 04:25:55 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-27 04:25:55 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-27 04:25:55 (7587) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-27 04:25:55 (7587) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-27 04:25:55 (7587) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-27 04:25:55 (7587) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-27 04:25:55 (7587) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-27 04:25:55 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-27 04:25:55 (7587) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-27 04:25:55 (7604) [INFO] 
* 2024-08-27 04:26:00 (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 04:26:00 (1974) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-27 04:26:01 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-27 04:26:02 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pj2gwFJo6h/ea_profile.json
* 2024-08-27 04:26: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/pj2gwFJo6h/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-27 04:26:04 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-28 04:25:37 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-28 04:25:37 (8939) [INFO] Script is up to date.
* 2024-08-28 04:25:39 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-28 04:25:39 (7574) [INFO] 
* 2024-08-28 04:25:43 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-28 04:25:43 (7574) [INFO] 
* 2024-08-28 04:25:50 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-28 04:25:50 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-28 04:25:50 (2104) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-28 04:25:53 (1963) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-28 04:25:53 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-28 04:25:53 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-28 04:25:53 (7574) [INFO] 
* 2024-08-28 04:25:53 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-28 04:25:53 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-28 04:25:53 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-28 04:25:53 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-28 04:25:53 (7587) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-28 04:25:53 (7587) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-28 04:25:53 (7587) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-28 04:25:53 (7587) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-28 04:25:53 (7587) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-28 04:25:53 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-28 04:25:53 (7587) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-28 04:25:53 (7604) [INFO] 
* 2024-08-28 04:25:58 (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 04:25:58 (1974) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-28 04:25:58 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-28 04:25:59 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ucLnaReXq0/ea_profile.json
* 2024-08-28 04:26: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/ucLnaReXq0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-28 04:26:01 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-29 04:25:45 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-29 04:25:45 (8939) [INFO] Script is up to date.
* 2024-08-29 04:25:46 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-29 04:25:46 (7574) [INFO] 
* 2024-08-29 04:25:50 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-29 04:25:50 (7574) [INFO] 
* 2024-08-29 04:25:57 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-29 04:25:57 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-29 04:25:57 (2104) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-29 04:26:01 (1963) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-29 04:26:01 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-29 04:26:01 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-29 04:26:01 (7574) [INFO] 
* 2024-08-29 04:26:01 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-29 04:26:02 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-29 04:26:02 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-29 04:26:02 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-29 04:26:02 (7587) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-29 04:26:02 (7587) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-29 04:26:02 (7587) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-29 04:26:02 (7587) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-29 04:26:02 (7587) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-29 04:26:02 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-29 04:26:02 (7587) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-29 04:26:02 (7604) [INFO] 
* 2024-08-29 04:26:07 (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 04:26:07 (1974) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-29 04:26:07 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-29 04:26:08 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HeAhYWr1yd/ea_profile.json
* 2024-08-29 04:26:11 (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/HeAhYWr1yd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-29 04:26:11 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-30 04:25:38 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-30 04:25:38 (8922) [INFO] Newer version of script found. Downloading.
* 2024-08-30 04:25:38 (8931) [INFO] Script update to version 53 successful.
* 2024-08-30 04:25:40 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-30 04:25:40 (7647) [INFO] 
* 2024-08-30 04:25:42 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-08-30 04:25:42 (7647) [INFO] 
* 2024-08-30 04:25:49 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-30 04:25:49 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-30 04:25:49 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-30 04:25:52 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-30 04:25:52 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-30 04:25:52 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-08-30 04:25:52 (7647) [INFO] 
* 2024-08-30 04:25:52 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-30 04:25:52 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-30 04:25:52 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-30 04:25:52 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-30 04:25:52 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-30 04:25:52 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-30 04:25:52 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-30 04:25:52 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-30 04:25:52 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-30 04:25:52 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-08-30 04:25:52 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-30 04:25:52 (7677) [INFO] 
* 2024-08-30 04:25: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-08-30 04:25:56 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-30 04:25:56 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-30 04:25:57 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rK8wxhKMOh/ea_profile.json
* 2024-08-30 04:25:59 (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/rK8wxhKMOh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-08-30 04:25:59 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-31 04:26:30 (8992) [INFO] Self-update of script version 53 requested.
* 2024-08-31 04:26:30 (9014) [INFO] Script is up to date.
* 2024-08-31 04:26:32 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-31 04:26:32 (7647) [INFO] 
* 2024-08-31 04:26:34 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-08-31 04:26:34 (7647) [INFO] 
* 2024-08-31 04:26:41 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-08-31 04:26:41 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-08-31 04:26:41 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-08-31 04:26:43 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-31 04:26:43 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-31 04:26:43 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-08-31 04:26:43 (7647) [INFO] 
* 2024-08-31 04:26:43 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-31 04:26:43 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-08-31 04:26:43 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-31 04:26:43 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-31 04:26:43 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-08-31 04:26:43 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-08-31 04:26:43 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-08-31 04:26:43 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-08-31 04:26:43 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-08-31 04:26:43 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-08-31 04:26:43 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-08-31 04:26:43 (7677) [INFO] 
* 2024-08-31 04:26:47 (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 04:26:47 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-31 04:26:47 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-31 04:26:48 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iV0jM7VFPs/ea_profile.json
* 2024-08-31 04:26:50 (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/iV0jM7VFPs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-08-31 04:26:50 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-01 04:26:25 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-01 04:26:25 (9014) [INFO] Script is up to date.
* 2024-09-01 04:26:26 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-01 04:26:26 (7647) [INFO] 
* 2024-09-01 04:26:30 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-01 04:26:30 (7647) [INFO] 
* 2024-09-01 04:26:37 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-01 04:26:37 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-01 04:26:37 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-01 04:26:39 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-01 04:26:39 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-01 04:26:39 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-01 04:26:39 (7647) [INFO] 
* 2024-09-01 04:26:39 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-01 04:26:40 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-01 04:26:40 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-01 04:26:40 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-01 04:26:40 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-01 04:26:40 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-01 04:26:40 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-01 04:26:40 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-01 04:26:40 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-01 04:26:40 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-01 04:26:40 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-01 04:26:40 (7677) [INFO] 
* 2024-09-01 04:26:44 (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 04:26:44 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-01 04:26:44 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-01 04:26:45 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qD1Z3fscuf/ea_profile.json
* 2024-09-01 04:26: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/qD1Z3fscuf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-01 04:26:47 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-02 04:25:31 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-02 04:25:31 (9014) [INFO] Script is up to date.
* 2024-09-02 04:25:33 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-02 04:25:33 (7647) [INFO] 
* 2024-09-02 04:25:36 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-02 04:25:36 (7647) [INFO] 
* 2024-09-02 04:25:44 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-02 04:25:44 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-02 04:25:44 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-02 04:25:47 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-02 04:25:47 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-02 04:25:47 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-02 04:25:47 (7647) [INFO] 
* 2024-09-02 04:25:47 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-02 04:25:47 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-02 04:25:47 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-02 04:25:47 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-02 04:25:47 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-02 04:25:47 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-02 04:25:47 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-02 04:25:47 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-02 04:25:47 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-02 04:25:47 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-02 04:25:47 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-02 04:25:47 (7677) [INFO] 
* 2024-09-02 04:25:52 (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 04:25:52 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-02 04:25:52 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-02 04:25:53 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aWOh4qn4uk/ea_profile.json
* 2024-09-02 04:25:56 (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/aWOh4qn4uk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-02 04:25:56 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-03 04:25:39 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-03 04:25:39 (9014) [INFO] Script is up to date.
* 2024-09-03 04:25:41 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-03 04:25:41 (7647) [INFO] 
* 2024-09-03 04:25:44 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-03 04:25:44 (7647) [INFO] 
* 2024-09-03 04:25:52 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-03 04:25:52 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-03 04:25:52 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-03 04:25:54 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-03 04:25:54 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-03 04:25:54 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-03 04:25:54 (7647) [INFO] 
* 2024-09-03 04:25:54 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-03 04:25:54 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-03 04:25:54 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-03 04:25:54 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-03 04:25:54 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-03 04:25:54 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-03 04:25:54 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-03 04:25:54 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-03 04:25:54 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-03 04:25:54 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-03 04:25:55 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-03 04:25:55 (7677) [INFO] 
* 2024-09-03 04:25:59 (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 04:25:59 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-03 04:26:00 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-03 04:26:01 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3GW5b4Xc92/ea_profile.json
* 2024-09-03 04:26:03 (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/3GW5b4Xc92/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-03 04:26:03 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-04 04:25:37 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-04 04:25:37 (9014) [INFO] Script is up to date.
* 2024-09-04 04:25:38 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-04 04:25:38 (7647) [INFO] 
* 2024-09-04 04:25:42 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-04 04:25:42 (7647) [INFO] 
* 2024-09-04 04:25:49 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-04 04:25:49 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-04 04:25:49 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-04 04:25:51 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-04 04:25:51 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-04 04:25:51 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-04 04:25:51 (7647) [INFO] 
* 2024-09-04 04:25:51 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-04 04:25:51 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-04 04:25:51 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-04 04:25:51 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-04 04:25:51 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-04 04:25:51 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-04 04:25:51 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-04 04:25:51 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-04 04:25:51 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-04 04:25:52 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-04 04:25:52 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-04 04:25:52 (7677) [INFO] 
* 2024-09-04 04:25: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-04 04:25:56 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-04 04:25:56 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-04 04:25:57 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3kguSeMPe4/ea_profile.json
* 2024-09-04 04:25:58 (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/3kguSeMPe4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-04 04:25:58 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-05 04:25:34 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-05 04:25:35 (9014) [INFO] Script is up to date.
* 2024-09-05 04:25:36 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-05 04:25:36 (7647) [INFO] 
* 2024-09-05 04:25:38 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-05 04:25:38 (7647) [INFO] 
* 2024-09-05 04:25:45 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-05 04:25:45 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-05 04:25:45 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-05 04:25:47 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-05 04:25:47 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-05 04:25:47 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-05 04:25:47 (7647) [INFO] 
* 2024-09-05 04:25:47 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-05 04:25:47 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-05 04:25:47 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-05 04:25:47 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-05 04:25:47 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-05 04:25:47 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-05 04:25:47 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-05 04:25:47 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-05 04:25:47 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-05 04:25:47 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-05 04:25:47 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-05 04:25:47 (7677) [INFO] 
* 2024-09-05 04:25: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-05 04:25:51 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-05 04:25:51 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-05 04:25:52 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KnM5VG454l/ea_profile.json
* 2024-09-05 04:25:54 (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/KnM5VG454l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-05 04:25:54 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-06 04:25:38 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-06 04:25:38 (9014) [INFO] Script is up to date.
* 2024-09-06 04:25:39 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-06 04:25:39 (7647) [INFO] 
* 2024-09-06 04:25:41 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-06 04:25:41 (7647) [INFO] 
* 2024-09-06 04:25:49 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-06 04:25:49 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-06 04:25:49 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-06 04:25:51 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-06 04:25:51 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-06 04:25:51 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-06 04:25:51 (7647) [INFO] 
* 2024-09-06 04:25:51 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-06 04:25:51 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-06 04:25:51 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-06 04:25:51 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-06 04:25:51 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-06 04:25:51 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-06 04:25:51 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-06 04:25:51 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-06 04:25:51 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-06 04:25:51 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-06 04:25:51 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-06 04:25:52 (7677) [INFO] 
* 2024-09-06 04:25: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-06 04:25:56 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-06 04:25:56 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-06 04:25:57 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8XIvTrK5sB/ea_profile.json
* 2024-09-06 04:25:59 (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/8XIvTrK5sB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-06 04:25:59 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-07 04:26:27 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-07 04:26:28 (9014) [INFO] Script is up to date.
* 2024-09-07 04:26:30 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-07 04:26:30 (7647) [INFO] 
* 2024-09-07 04:26:34 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-07 04:26:34 (7647) [INFO] 
* 2024-09-07 04:26:41 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-07 04:26:41 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-07 04:26:41 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-07 04:26:44 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-07 04:26:44 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-07 04:26:44 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-07 04:26:44 (7647) [INFO] 
* 2024-09-07 04:26:44 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-07 04:26:44 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-07 04:26:44 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-07 04:26:44 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-07 04:26:44 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-07 04:26:44 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-07 04:26:44 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-07 04:26:44 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-07 04:26:44 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-07 04:26:44 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-07 04:26:44 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-07 04:26:44 (7677) [INFO] 
* 2024-09-07 04:26:49 (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 04:26:49 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-07 04:26:49 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-07 04:26:50 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JiKOolLkDq/ea_profile.json
* 2024-09-07 04:26:53 (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/JiKOolLkDq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-07 04:26:53 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-08 04:26:27 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-08 04:26:27 (9014) [INFO] Script is up to date.
* 2024-09-08 04:26:28 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-08 04:26:28 (7647) [INFO] 
* 2024-09-08 04:26:32 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-08 04:26:32 (7647) [INFO] 
* 2024-09-08 04:26:51 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-08 04:26:51 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-08 04:26:51 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-08 04:26:54 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-08 04:26:54 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-08 04:26:54 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-08 04:26:54 (7647) [INFO] 
* 2024-09-08 04:26:54 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-08 04:26:54 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-08 04:26:54 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-08 04:26:54 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-08 04:26:54 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-08 04:26:54 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-08 04:26:54 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-08 04:26:54 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-08 04:26:54 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-08 04:26:54 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-08 04:26:54 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-08 04:26:54 (7677) [INFO] 
* 2024-09-08 04:26:59 (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 04:26:59 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-08 04:26:59 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-08 04:27:00 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Um3Qixb3pb/ea_profile.json
* 2024-09-08 04:27:02 (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/Um3Qixb3pb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-08 04:27:02 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-09 04:25:38 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-09 04:25:38 (9014) [INFO] Script is up to date.
* 2024-09-09 04:25:39 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-09 04:25:39 (7647) [INFO] 
* 2024-09-09 04:25:42 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-09 04:25:42 (7647) [INFO] 
* 2024-09-09 04:25:48 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-09 04:25:48 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-09 04:25:48 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-09 04:25:50 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-09 04:25:50 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-09 04:25:50 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-09 04:25:50 (7647) [INFO] 
* 2024-09-09 04:25:50 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-09 04:25:51 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-09 04:25:51 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-09 04:25:51 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-09 04:25:51 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-09 04:25:51 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-09 04:25:51 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-09 04:25:51 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-09 04:25:51 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-09 04:25:51 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-09 04:25:51 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-09 04:25:51 (7677) [INFO] 
* 2024-09-09 04:25: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-09 04:25:55 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-09 04:25:55 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-09 04:25:56 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p03dqKrGtv/ea_profile.json
* 2024-09-09 04:25:58 (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/p03dqKrGtv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-09 04:25:58 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-10 04:25:33 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-10 04:25:33 (9014) [INFO] Script is up to date.
* 2024-09-10 04:25:35 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-10 04:25:35 (7647) [INFO] 
* 2024-09-10 04:25:38 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-10 04:25:38 (7647) [INFO] 
* 2024-09-10 04:25:46 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-10 04:25:46 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-10 04:25:46 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-10 04:25:49 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-10 04:25:49 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-10 04:25:49 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-10 04:25:49 (7647) [INFO] 
* 2024-09-10 04:25:49 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-10 04:25:49 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-10 04:25:49 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-10 04:25:49 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-10 04:25:49 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-10 04:25:49 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-10 04:25:49 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-10 04:25:49 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-10 04:25:49 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-10 04:25:49 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-10 04:25:49 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-10 04:25:49 (7677) [INFO] 
* 2024-09-10 04:25:54 (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 04:25:54 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-10 04:25:54 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-10 04:25:55 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iPG4wpO034/ea_profile.json
* 2024-09-10 04:25: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/iPG4wpO034/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-10 04:25:57 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-11 04:25:32 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-11 04:25:32 (9014) [INFO] Script is up to date.
* 2024-09-11 04:25:34 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-11 04:25:34 (7647) [INFO] 
* 2024-09-11 04:25:39 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-11 04:25:39 (7647) [INFO] 
* 2024-09-11 04:25:46 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-11 04:25:46 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-11 04:25:46 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-11 04:25:48 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-11 04:25:48 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-11 04:25:48 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-11 04:25:48 (7647) [INFO] 
* 2024-09-11 04:25:48 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-11 04:25:48 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-11 04:25:48 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-11 04:25:48 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-11 04:25:48 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-11 04:25:48 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-11 04:25:48 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-11 04:25:48 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-11 04:25:48 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-11 04:25:48 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-11 04:25:48 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-11 04:25:48 (7677) [INFO] 
* 2024-09-11 04:25:53 (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 04:25:53 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-11 04:25:53 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-11 04:25:54 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tB1YvrJtiU/ea_profile.json
* 2024-09-11 04:25:56 (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/tB1YvrJtiU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-11 04:25:56 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-12 04:25:34 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-12 04:25:34 (9014) [INFO] Script is up to date.
* 2024-09-12 04:25:35 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-12 04:25:35 (7647) [INFO] 
* 2024-09-12 04:25:38 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-12 04:25:38 (7647) [INFO] 
* 2024-09-12 04:25:46 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-12 04:25:46 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-12 04:25:46 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-12 04:25:49 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-12 04:25:49 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-12 04:25:49 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-12 04:25:49 (7647) [INFO] 
* 2024-09-12 04:25:49 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-12 04:25:49 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-12 04:25:49 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-12 04:25:49 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-12 04:25:49 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-12 04:25:49 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-12 04:25:49 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-12 04:25:49 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-12 04:25:49 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-12 04:25:49 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-12 04:25:49 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-12 04:25:49 (7677) [INFO] 
* 2024-09-12 04:25:54 (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 04:25:54 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-12 04:25:55 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-12 04:25:55 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KrxCRG8lZD/ea_profile.json
* 2024-09-12 04:25:58 (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/KrxCRG8lZD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-12 04:25:58 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-13 04:25:41 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-13 04:25:41 (9014) [INFO] Script is up to date.
* 2024-09-13 04:25:42 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-13 04:25:42 (7647) [INFO] 
* 2024-09-13 04:25:45 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-13 04:25:45 (7647) [INFO] 
* 2024-09-13 04:25:53 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-13 04:25:53 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-13 04:25:53 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-13 04:25:56 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-13 04:25:56 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-13 04:25:56 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-13 04:25:56 (7647) [INFO] 
* 2024-09-13 04:25:57 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-13 04:25:57 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-13 04:25:57 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-13 04:25:57 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-13 04:25:57 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-13 04:25:57 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-13 04:25:57 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-13 04:25:57 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-13 04:25:57 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-13 04:25:57 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-13 04:25:57 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-13 04:25:57 (7677) [INFO] 
* 2024-09-13 04:26:03 (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 04:26:03 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-13 04:26:04 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-13 04:26:05 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Hca9_n55Ck/ea_profile.json
* 2024-09-13 04:26:09 (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/Hca9_n55Ck/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-13 04:26:09 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-14 04:26:24 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-14 04:26:24 (9014) [INFO] Script is up to date.
* 2024-09-14 04:26:25 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-14 04:26:25 (7647) [INFO] 
* 2024-09-14 04:26:28 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-14 04:26:28 (7647) [INFO] 
* 2024-09-14 04:26:33 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-14 04:26:33 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-14 04:26:33 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-14 04:26:35 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-14 04:26:35 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-14 04:26:35 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-14 04:26:35 (7647) [INFO] 
* 2024-09-14 04:26:35 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-14 04:26:35 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-14 04:26:35 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-14 04:26:35 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-14 04:26:35 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-14 04:26:35 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-14 04:26:35 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-14 04:26:35 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-14 04:26:35 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-14 04:26:35 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-14 04:26:35 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-14 04:26:35 (7677) [INFO] 
* 2024-09-14 04:26:40 (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 04:26:40 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-14 04:26:40 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-14 04:26:41 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WwWrMjFhh6/ea_profile.json
* 2024-09-14 04:26: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/WwWrMjFhh6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-14 04:26:42 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-15 04:26:21 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-15 04:26:21 (9014) [INFO] Script is up to date.
* 2024-09-15 04:26:22 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-15 04:26:22 (7647) [INFO] 
* 2024-09-15 04:26:25 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-15 04:26:25 (7647) [INFO] 
* 2024-09-15 04:26:32 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-15 04:26:32 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-15 04:26:32 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-15 04:26:34 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-15 04:26:34 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-15 04:26:34 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-15 04:26:34 (7647) [INFO] 
* 2024-09-15 04:26:34 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-15 04:26:34 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-15 04:26:34 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-15 04:26:34 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-15 04:26:34 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-15 04:26:34 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-15 04:26:34 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-15 04:26:34 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-15 04:26:34 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-15 04:26:34 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-15 04:26:34 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-15 04:26:34 (7677) [INFO] 
* 2024-09-15 04:26: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-15 04:26:38 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-15 04:26:38 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-15 04:26:39 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BHbJJMokkE/ea_profile.json
* 2024-09-15 04:26:41 (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/BHbJJMokkE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-15 04:26:41 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-16 04:25:33 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-16 04:25:34 (9014) [INFO] Script is up to date.
* 2024-09-16 04:25:36 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-16 04:25:36 (7647) [INFO] 
* 2024-09-16 04:25:40 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-16 04:25:40 (7647) [INFO] 
* 2024-09-16 04:25:47 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-16 04:25:47 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-16 04:25:47 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-16 04:25:50 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-16 04:25:50 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-16 04:25:50 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-16 04:25:50 (7647) [INFO] 
* 2024-09-16 04:25:50 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-16 04:25:50 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-16 04:25:50 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-16 04:25:50 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-16 04:25:50 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-16 04:25:50 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-16 04:25:50 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-16 04:25:50 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-16 04:25:50 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-16 04:25:50 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-16 04:25:50 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-16 04:25:50 (7677) [INFO] 
* 2024-09-16 04:25: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-16 04:25:55 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-16 04:25:55 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-16 04:25:56 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/12aUQ5nRQo/ea_profile.json
* 2024-09-16 04:25:59 (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/12aUQ5nRQo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-16 04:25:59 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-17 04:25:39 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-17 04:25:39 (9014) [INFO] Script is up to date.
* 2024-09-17 04:25:40 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-17 04:25:40 (7647) [INFO] 
* 2024-09-17 04:25:43 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-17 04:25:43 (7647) [INFO] 
* 2024-09-17 04:25:54 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-17 04:25:54 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-17 04:25:54 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-17 04:25:57 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-17 04:25:57 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-17 04:25:57 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-17 04:25:57 (7647) [INFO] 
* 2024-09-17 04:25:57 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-17 04:25:57 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-17 04:25:57 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-17 04:25:57 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-17 04:25:57 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-17 04:25:57 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-17 04:25:57 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-17 04:25:57 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-17 04:25:57 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-17 04:25:57 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-17 04:25:57 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-17 04:25:57 (7677) [INFO] 
* 2024-09-17 04:26: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-09-17 04:26:02 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-17 04:26:02 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-17 04:26:03 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/a3DFich5_E/ea_profile.json
* 2024-09-17 04:26: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/a3DFich5_E/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-17 04:26:05 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-18 04:25:32 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-18 04:25:33 (9014) [INFO] Script is up to date.
* 2024-09-18 04:25:35 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-18 04:25:35 (7647) [INFO] 
* 2024-09-18 04:25:39 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-18 04:25:39 (7647) [INFO] 
* 2024-09-18 04:25:45 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-18 04:25:45 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-18 04:25:45 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-18 04:25:48 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-18 04:25:48 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-18 04:25:48 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-18 04:25:48 (7647) [INFO] 
* 2024-09-18 04:25:48 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-18 04:25:48 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-18 04:25:48 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-18 04:25:48 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-18 04:25:48 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-18 04:25:48 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-18 04:25:48 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-18 04:25:48 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-18 04:25:48 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-18 04:25:48 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-18 04:25:48 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-18 04:25:48 (7677) [INFO] 
* 2024-09-18 04:25:53 (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 04:25:53 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-18 04:25:53 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-18 04:25:54 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lKzxhfvh__/ea_profile.json
* 2024-09-18 04:25: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/lKzxhfvh__/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-18 04:25:57 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-19 04:27:08 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-19 04:27:08 (9014) [INFO] Script is up to date.
* 2024-09-19 04:27:10 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-19 04:27:10 (7647) [INFO] 
* 2024-09-19 04:27:14 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-19 04:27:14 (7647) [INFO] 
* 2024-09-19 04:27:20 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-19 04:27:20 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-19 04:27:20 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-19 04:27:22 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-19 04:27:22 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-19 04:27:22 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-19 04:27:22 (7647) [INFO] 
* 2024-09-19 04:27:22 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-19 04:27:22 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-19 04:27:22 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-19 04:27:22 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-19 04:27:22 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-19 04:27:22 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-19 04:27:22 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-19 04:27:22 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-19 04:27:22 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-19 04:27:22 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-19 04:27:22 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-19 04:27:22 (7677) [INFO] 
* 2024-09-19 04:27:27 (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 04:27:27 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-19 04:27:28 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-19 04:27:28 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/42MBXqLf6I/ea_profile.json
* 2024-09-19 04:27: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/42MBXqLf6I/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-19 04:27:30 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-20 04:25:33 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-20 04:25:33 (9014) [INFO] Script is up to date.
* 2024-09-20 04:25:35 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-20 04:25:35 (7647) [INFO] 
* 2024-09-20 04:25:39 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-20 04:25:39 (7647) [INFO] 
* 2024-09-20 04:25:49 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-20 04:25:49 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-20 04:25:49 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-20 04:25:51 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-20 04:25:51 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-20 04:25:51 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-20 04:25:51 (7647) [INFO] 
* 2024-09-20 04:25:52 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-20 04:25:52 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-20 04:25:52 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-20 04:25:52 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-20 04:25:52 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-20 04:25:52 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-20 04:25:52 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-20 04:25:52 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-20 04:25:52 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-20 04:25:52 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-20 04:25:52 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-20 04:25:52 (7677) [INFO] 
* 2024-09-20 04:25: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-20 04:25:58 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-20 04:25:58 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-20 04:25:59 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UiYrqyDlLQ/ea_profile.json
* 2024-09-20 04:26: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/UiYrqyDlLQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-20 04:26:01 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-21 04:27:09 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-21 04:27:09 (9014) [INFO] Script is up to date.
* 2024-09-21 04:27:12 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-21 04:27:12 (7647) [INFO] 
* 2024-09-21 04:27:17 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-21 04:27:17 (7647) [INFO] 
* 2024-09-21 04:27:24 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-21 04:27:24 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-21 04:27:24 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-21 04:27:26 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-21 04:27:26 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-21 04:27:26 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-21 04:27:26 (7647) [INFO] 
* 2024-09-21 04:27:26 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-21 04:27:26 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-21 04:27:26 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-21 04:27:26 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-21 04:27:26 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-21 04:27:26 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-21 04:27:26 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-21 04:27:26 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-21 04:27:26 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-21 04:27:26 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-21 04:27:26 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-21 04:27:26 (7677) [INFO] 
* 2024-09-21 04:27: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-21 04:27:32 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-21 04:27:32 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-21 04:27:33 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qzQVlDCJq5/ea_profile.json
* 2024-09-21 04:27:34 (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/qzQVlDCJq5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-21 04:27:34 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-22 04:26:25 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-22 04:26:25 (9014) [INFO] Script is up to date.
* 2024-09-22 04:26:27 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-22 04:26:27 (7647) [INFO] 
* 2024-09-22 04:26:29 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-22 04:26:29 (7647) [INFO] 
* 2024-09-22 04:26:40 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-22 04:26:40 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-22 04:26:40 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-22 04:26:42 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-22 04:26:42 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-22 04:26:42 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-22 04:26:42 (7647) [INFO] 
* 2024-09-22 04:26:42 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-22 04:26:42 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-22 04:26:42 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-22 04:26:42 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-22 04:26:42 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-22 04:26:42 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-22 04:26:42 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-22 04:26:42 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-22 04:26:42 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-22 04:26:42 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-22 04:26:42 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-22 04:26:42 (7677) [INFO] 
* 2024-09-22 04:26:47 (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 04:26:47 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-22 04:26:48 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-22 04:26:48 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BvVn5VBStG/ea_profile.json
* 2024-09-22 04:26:51 (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/BvVn5VBStG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-22 04:26:51 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-23 04:25:34 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-23 04:25:34 (9014) [INFO] Script is up to date.
* 2024-09-23 04:25:36 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-23 04:25:36 (7647) [INFO] 
* 2024-09-23 04:25:38 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-23 04:25:38 (7647) [INFO] 
* 2024-09-23 04:25:45 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-23 04:25:45 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-23 04:25:45 (2107) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-23 04:25:48 (1966) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-23 04:25:48 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-23 04:25:48 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-23 04:25:48 (7647) [INFO] 
* 2024-09-23 04:25:48 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-23 04:25:48 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-23 04:25:48 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-23 04:25:48 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-23 04:25:48 (7660) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-23 04:25:48 (7660) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-23 04:25:48 (7660) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-23 04:25:48 (7660) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-23 04:25:48 (7660) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-23 04:25:48 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-23 04:25:48 (7660) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-23 04:25:48 (7677) [INFO] 
* 2024-09-23 04:25:53 (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 04:25:53 (1977) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-23 04:25:53 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-23 04:25:54 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/H17OjjQGJw/ea_profile.json
* 2024-09-23 04:25: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/H17OjjQGJw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-23 04:25:57 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-24 04:25:45 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-24 04:25:45 (8997) [INFO] Newer version of script found. Downloading.
* 2024-09-24 04:25:46 (9006) [INFO] Script update to version 54 successful.
* 2024-09-24 04:25:47 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-24 04:25:47 (7667) [INFO] 
* 2024-09-24 04:25:51 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-24 04:25:51 (7667) [INFO] 
* 2024-09-24 04:25:57 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-24 04:25:57 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-24 04:25:57 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-24 04:26:00 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-24 04:26:00 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-24 04:26:00 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-24 04:26:00 (7667) [INFO] 
* 2024-09-24 04:26:01 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-24 04:26:01 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-24 04:26:01 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-24 04:26:01 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-24 04:26:01 (7680) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-24 04:26:01 (7680) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-24 04:26:01 (7680) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-24 04:26:01 (7680) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-24 04:26:01 (7680) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-24 04:26:01 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-24 04:26:01 (7680) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-24 04:26:01 (7697) [INFO] 
* 2024-09-24 04:26:06 (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 04:26:06 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-24 04:26:06 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-24 04:26:07 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zF3mlzDDrU/ea_profile.json
* 2024-09-24 04:26: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/zF3mlzDDrU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-24 04:26:09 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-25 04:25:33 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-25 04:25:33 (9030) [INFO] Script is up to date.
* 2024-09-25 04:25:34 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-25 04:25:34 (7667) [INFO] 
* 2024-09-25 04:25:37 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-25 04:25:37 (7667) [INFO] 
* 2024-09-25 04:25:53 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-25 04:25:53 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-25 04:25:53 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-25 04:25:54 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-25 04:25:54 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-25 04:25:54 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-25 04:25:54 (7667) [INFO] 
* 2024-09-25 04:25:55 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-25 04:25:55 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-25 04:25:55 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-25 04:25:55 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-25 04:25:55 (7680) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-25 04:25:55 (7680) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-25 04:25:55 (7680) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-25 04:25:55 (7680) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-25 04:25:55 (7680) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-25 04:25:55 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-25 04:25:55 (7680) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-25 04:25:55 (7697) [INFO] 
* 2024-09-25 04:25:59 (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 04:25:59 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-25 04:25:59 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-25 04:26:00 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WGp92LKnUw/ea_profile.json
* 2024-09-25 04:26: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/WGp92LKnUw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-25 04:26:03 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-26 04:25:37 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-26 04:25:37 (9030) [INFO] Script is up to date.
* 2024-09-26 04:25:38 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-26 04:25:38 (7667) [INFO] 
* 2024-09-26 04:25:41 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-26 04:25:41 (7667) [INFO] 
* 2024-09-26 04:25:48 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-26 04:25:48 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-26 04:25:48 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-26 04:25:51 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-26 04:25:51 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-26 04:25:51 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-26 04:25:51 (7667) [INFO] 
* 2024-09-26 04:25:51 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-26 04:25:51 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-26 04:25:51 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-26 04:25:51 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-26 04:25:51 (7680) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-26 04:25:51 (7680) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-26 04:25:51 (7680) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-26 04:25:51 (7680) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-26 04:25:51 (7680) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-26 04:25:51 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-26 04:25:51 (7680) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-26 04:25:51 (7697) [INFO] 
* 2024-09-26 04:25: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-09-26 04:25:56 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-26 04:25:57 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-26 04:25:57 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5tFlgXiz72/ea_profile.json
* 2024-09-26 04:26: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/5tFlgXiz72/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-26 04:26:00 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-27 04:25:39 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-27 04:25:40 (9030) [INFO] Script is up to date.
* 2024-09-27 04:25:41 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-27 04:25:41 (7667) [INFO] 
* 2024-09-27 04:25:44 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-27 04:25:44 (7667) [INFO] 
* 2024-09-27 04:25:51 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-27 04:25:51 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-27 04:25:51 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-27 04:25:54 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-27 04:25:54 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-27 04:25:54 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-27 04:25:54 (7667) [INFO] 
* 2024-09-27 04:25:54 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-27 04:25:54 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-27 04:25:54 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-27 04:25:54 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-27 04:25:54 (7680) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-27 04:25:54 (7680) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-27 04:25:54 (7680) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-27 04:25:54 (7680) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-27 04:25:54 (7680) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-27 04:25:54 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-27 04:25:54 (7680) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-27 04:25:54 (7697) [INFO] 
* 2024-09-27 04:26: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-09-27 04:26:00 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-27 04:26:00 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-27 04:26:01 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/n2QMIP5tdI/ea_profile.json
* 2024-09-27 04:26: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/n2QMIP5tdI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-27 04:26:04 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-28 04:26:27 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-28 04:26:27 (9030) [INFO] Script is up to date.
* 2024-09-28 04:26:28 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-28 04:26:28 (7667) [INFO] 
* 2024-09-28 04:26:32 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-28 04:26:32 (7667) [INFO] 
* 2024-09-28 04:26:39 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-28 04:26:39 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-28 04:26:39 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-28 04:26:42 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-28 04:26:42 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-28 04:26:42 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-28 04:26:42 (7667) [INFO] 
* 2024-09-28 04:26:42 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-28 04:26:42 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-28 04:26:42 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-28 04:26:42 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-28 04:26:42 (7680) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-28 04:26:42 (7680) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-28 04:26:42 (7680) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-28 04:26:42 (7680) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-28 04:26:42 (7680) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-28 04:26:42 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-28 04:26:42 (7680) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-28 04:26:42 (7697) [INFO] 
* 2024-09-28 04:26:47 (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 04:26:47 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-28 04:26:47 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-28 04:26:48 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PZbLLGUd_z/ea_profile.json
* 2024-09-28 04:26:51 (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/PZbLLGUd_z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-28 04:26:51 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-29 04:26:25 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-29 04:26:25 (9030) [INFO] Script is up to date.
* 2024-09-29 04:26:27 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-29 04:26:27 (7667) [INFO] 
* 2024-09-29 04:26:30 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-29 04:26:30 (7667) [INFO] 
* 2024-09-29 04:26:36 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-29 04:26:36 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-29 04:26:36 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-29 04:26:39 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-29 04:26:39 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-29 04:26:39 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-29 04:26:39 (7667) [INFO] 
* 2024-09-29 04:26:39 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-29 04:26:39 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-29 04:26:39 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-29 04:26:39 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-29 04:26:39 (7680) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-29 04:26:39 (7680) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-29 04:26:39 (7680) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-29 04:26:39 (7680) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-29 04:26:39 (7680) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-29 04:26:39 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-29 04:26:39 (7680) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-29 04:26:39 (7697) [INFO] 
* 2024-09-29 04:26:45 (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 04:26:45 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-29 04:26:45 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-29 04:26:46 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yM5KoK62HE/ea_profile.json
* 2024-09-29 04:26: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/yM5KoK62HE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-29 04:26:48 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-30 04:25:34 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-30 04:25:34 (9030) [INFO] Script is up to date.
* 2024-09-30 04:25:36 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-30 04:25:36 (7667) [INFO] 
* 2024-09-30 04:25:39 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-30 04:25:39 (7667) [INFO] 
* 2024-09-30 04:25:45 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-09-30 04:25:45 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-09-30 04:25:45 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-09-30 04:25:46 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-30 04:25:46 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-30 04:25:46 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-30 04:25:46 (7667) [INFO] 
* 2024-09-30 04:25:46 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-30 04:25:47 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-09-30 04:25:47 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-30 04:25:47 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-30 04:25:47 (7680) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-09-30 04:25:47 (7680) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-09-30 04:25:47 (7680) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-09-30 04:25:47 (7680) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-09-30 04:25:47 (7680) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-09-30 04:25:47 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-30 04:25:47 (7680) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-09-30 04:25:47 (7697) [INFO] 
* 2024-09-30 04:25: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-09-30 04:25:51 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-30 04:25:51 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-30 04:25:52 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6bhrqVnQ_Y/ea_profile.json
* 2024-09-30 04:25:54 (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/6bhrqVnQ_Y/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-30 04:25:54 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-01 04:25:34 (9008) [INFO] Self-update of script version 54 requested.
* 2024-10-01 04:25:34 (9013) [INFO] Newer version of script found. Downloading.
* 2024-10-01 04:25:34 (9022) [INFO] Script update to version 55 successful.
* 2024-10-01 04:25:36 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-01 04:25:36 (7668) [INFO] 
* 2024-10-01 04:25:38 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-01 04:25:38 (7668) [INFO] 
* 2024-10-01 04:25:45 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-01 04:25:45 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-01 04:25:45 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-01 04:25:48 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-01 04:25:48 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-01 04:25:48 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-01 04:25:48 (7668) [INFO] 
* 2024-10-01 04:25:48 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-01 04:25:48 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-01 04:25:48 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-01 04:25:48 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-01 04:25:48 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-01 04:25:48 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-01 04:25:48 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-01 04:25:48 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-01 04:25:48 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-01 04:25:48 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-01 04:25:48 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-01 04:25:48 (7698) [INFO] 
* 2024-10-01 04:25: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-01 04:25:53 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-01 04:25:53 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-01 04:25:54 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qojDAQDjs3/ea_profile.json
* 2024-10-01 04:25: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/qojDAQDjs3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-01 04:25:56 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-02 04:25:36 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-02 04:25:37 (9031) [INFO] Script is up to date.
* 2024-10-02 04:25:38 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-02 04:25:38 (7668) [INFO] 
* 2024-10-02 04:25:42 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-02 04:25:42 (7668) [INFO] 
* 2024-10-02 04:25:49 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-02 04:25:49 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-02 04:25:49 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-02 04:25:51 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-02 04:25:51 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-02 04:25:51 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-02 04:25:51 (7668) [INFO] 
* 2024-10-02 04:25:51 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-02 04:25:51 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-02 04:25:51 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-02 04:25:51 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-02 04:25:51 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-02 04:25:51 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-02 04:25:51 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-02 04:25:51 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-02 04:25:51 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-02 04:25:51 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-02 04:25:51 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-02 04:25:51 (7698) [INFO] 
* 2024-10-02 04:25: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-02 04:25:56 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-02 04:25:56 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-02 04:25:57 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xP4FuWEjm4/ea_profile.json
* 2024-10-02 04:25: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/xP4FuWEjm4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-02 04:25:59 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-03 04:26:19 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-03 04:26:19 (9031) [INFO] Script is up to date.
* 2024-10-03 04:26:21 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-03 04:26:21 (7668) [INFO] 
* 2024-10-03 04:26:26 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-03 04:26:26 (7668) [INFO] 
* 2024-10-03 04:26:32 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-03 04:26:32 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-03 04:26:32 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-03 04:26:34 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-03 04:26:34 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-03 04:26:34 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-03 04:26:34 (7668) [INFO] 
* 2024-10-03 04:26:35 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-03 04:26:35 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-03 04:26:35 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-03 04:26:35 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-03 04:26:35 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-03 04:26:35 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-03 04:26:35 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-03 04:26:35 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-03 04:26:35 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-03 04:26:35 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-03 04:26:35 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-03 04:26:35 (7698) [INFO] 
* 2024-10-03 04:26: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-10-03 04:26:41 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-03 04:26:41 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-03 04:26:42 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fpf_tB2i48/ea_profile.json
* 2024-10-03 04:26: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/fpf_tB2i48/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-03 04:26:44 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-04 04:25:35 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-04 04:25:35 (9031) [INFO] Script is up to date.
* 2024-10-04 04:25:37 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-04 04:25:37 (7668) [INFO] 
* 2024-10-04 04:25:39 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-04 04:25:39 (7668) [INFO] 
* 2024-10-04 04:25:46 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-04 04:25:46 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-04 04:25:46 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-04 04:25:47 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-04 04:25:47 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-04 04:25:47 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-04 04:25:47 (7668) [INFO] 
* 2024-10-04 04:25:48 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-04 04:25:48 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-04 04:25:48 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-04 04:25:48 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-04 04:25:48 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-04 04:25:48 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-04 04:25:48 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-04 04:25:48 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-04 04:25:48 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-04 04:25:48 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-04 04:25:48 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-04 04:25:48 (7698) [INFO] 
* 2024-10-04 04:25: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-04 04:25:53 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-04 04:25:53 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-04 04:25:54 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DGZYwHSxLM/ea_profile.json
* 2024-10-04 04:25: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/DGZYwHSxLM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-04 04:25:56 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-05 04:26:30 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-05 04:26:30 (9031) [INFO] Script is up to date.
* 2024-10-05 04:26:31 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-05 04:26:31 (7668) [INFO] 
* 2024-10-05 04:26:34 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-05 04:26:34 (7668) [INFO] 
* 2024-10-05 04:26:40 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-05 04:26:40 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-05 04:26:40 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-05 04:26:43 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-05 04:26:43 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-05 04:26:43 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-05 04:26:43 (7668) [INFO] 
* 2024-10-05 04:26:43 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-05 04:26:43 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-05 04:26:43 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-05 04:26:43 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-05 04:26:43 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-05 04:26:43 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-05 04:26:43 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-05 04:26:43 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-05 04:26:43 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-05 04:26:43 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-05 04:26:43 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-05 04:26:44 (7698) [INFO] 
* 2024-10-05 04:26:48 (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 04:26:48 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-05 04:26:49 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-05 04:26:49 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QjdllvXBDp/ea_profile.json
* 2024-10-05 04:26:52 (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/QjdllvXBDp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-05 04:26:52 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-06 04:26:22 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-06 04:26:22 (9031) [INFO] Script is up to date.
* 2024-10-06 04:26:24 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-06 04:26:24 (7668) [INFO] 
* 2024-10-06 04:26:28 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-06 04:26:28 (7668) [INFO] 
* 2024-10-06 04:26:34 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-06 04:26:34 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-06 04:26:34 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-06 04:26:36 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-06 04:26:36 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-06 04:26:36 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-06 04:26:36 (7668) [INFO] 
* 2024-10-06 04:26:36 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-06 04:26:36 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-06 04:26:36 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-06 04:26:36 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-06 04:26:36 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-06 04:26:36 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-06 04:26:36 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-06 04:26:36 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-06 04:26:36 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-06 04:26:36 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-06 04:26:36 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-06 04:26:36 (7698) [INFO] 
* 2024-10-06 04:26: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-06 04:26:40 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-06 04:26:40 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-06 04:26:41 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4U1Nr1PE9c/ea_profile.json
* 2024-10-06 04:26:43 (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/4U1Nr1PE9c/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-06 04:26:43 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-07 04:25:37 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-07 04:25:37 (9031) [INFO] Script is up to date.
* 2024-10-07 04:25:40 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-07 04:25:40 (7668) [INFO] 
* 2024-10-07 04:25:44 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-07 04:25:44 (7668) [INFO] 
* 2024-10-07 04:25:51 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-07 04:25:51 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-07 04:25:51 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-07 04:25:53 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-07 04:25:53 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-07 04:25:53 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-07 04:25:53 (7668) [INFO] 
* 2024-10-07 04:25:54 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-07 04:25:54 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-07 04:25:54 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-07 04:25:54 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-07 04:25:54 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-07 04:25:54 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-07 04:25:54 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-07 04:25:54 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-07 04:25:54 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-07 04:25:54 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-07 04:25:54 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-07 04:25:54 (7698) [INFO] 
* 2024-10-07 04:25:59 (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 04:25:59 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-07 04:25:59 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-07 04:26:00 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YcRH9WnA8J/ea_profile.json
* 2024-10-07 04:26: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/YcRH9WnA8J/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-07 04:26:02 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-08 04:25:39 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-08 04:25:39 (9031) [INFO] Script is up to date.
* 2024-10-08 04:25:40 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-08 04:25:40 (7668) [INFO] 
* 2024-10-08 04:28:06 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-08 04:28:06 (7668) [INFO] 
* 2024-10-08 04:28:13 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-08 04:28:13 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-08 04:28:13 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-08 04:28:16 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-08 04:28:16 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-08 04:28:16 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-08 04:28:16 (7668) [INFO] 
* 2024-10-08 04:28:16 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-08 04:28:16 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-08 04:28:16 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-08 04:28:16 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-08 04:28:16 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-08 04:28:16 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-08 04:28:16 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-08 04:28:16 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-08 04:28:16 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-08 04:28:16 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-08 04:28:16 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-08 04:28:16 (7698) [INFO] 
* 2024-10-08 04:28:21 (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 04:28:21 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-08 04:28:21 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-08 04:28:22 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aL2aDcUQJm/ea_profile.json
* 2024-10-08 04:28:24 (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/aL2aDcUQJm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-08 04:28:24 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-09 04:25:33 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-09 04:25:33 (9031) [INFO] Script is up to date.
* 2024-10-09 04:25:34 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-09 04:25:34 (7668) [INFO] 
* 2024-10-09 04:25:36 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-09 04:25:36 (7668) [INFO] 
* 2024-10-09 04:25:43 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-09 04:25:43 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-09 04:25:43 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-09 04:25:45 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-09 04:25:45 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-09 04:25:45 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-09 04:25:45 (7668) [INFO] 
* 2024-10-09 04:25:45 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-09 04:25:45 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-09 04:25:45 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-09 04:25:45 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-09 04:25:45 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-09 04:25:45 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-09 04:25:45 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-09 04:25:45 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-09 04:25:45 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-09 04:25:45 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-09 04:25:45 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-09 04:25:45 (7698) [INFO] 
* 2024-10-09 04:25:49 (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 04:25:49 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-09 04:25:50 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-09 04:25:51 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CgClD3F_Ei/ea_profile.json
* 2024-10-09 04:25:52 (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/CgClD3F_Ei/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-09 04:25:52 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-10 04:25:35 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-10 04:25:35 (9031) [INFO] Script is up to date.
* 2024-10-10 04:25:36 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-10 04:25:36 (7668) [INFO] 
* 2024-10-10 04:25:39 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-10 04:25:39 (7668) [INFO] 
* 2024-10-10 04:25:47 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-10 04:25:47 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-10 04:25:47 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-10 04:25:49 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-10 04:25:49 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-10 04:25:49 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-10 04:25:49 (7668) [INFO] 
* 2024-10-10 04:25:50 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-10 04:25:50 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-10 04:25:50 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-10 04:25:50 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-10 04:25:50 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-10 04:25:50 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-10 04:25:50 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-10 04:25:50 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-10 04:25:50 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-10 04:25:50 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-10 04:25:50 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-10 04:25:50 (7698) [INFO] 
* 2024-10-10 04:25: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-10 04:25:55 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-10 04:25:55 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-10 04:25:56 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SYVC7X0izi/ea_profile.json
* 2024-10-10 04:25:58 (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/SYVC7X0izi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-10 04:25:58 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-11 04:25:39 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-11 04:25:39 (9031) [INFO] Script is up to date.
* 2024-10-11 04:25:40 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-11 04:25:40 (7668) [INFO] 
* 2024-10-11 04:25:44 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-11 04:25:44 (7668) [INFO] 
* 2024-10-11 04:25:51 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-11 04:25:51 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-11 04:25:51 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-11 04:25:54 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-11 04:25:54 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-11 04:25:54 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-11 04:25:54 (7668) [INFO] 
* 2024-10-11 04:25:54 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-11 04:25:54 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-11 04:25:54 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-11 04:25:54 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-11 04:25:54 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-11 04:25:54 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-11 04:25:54 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-11 04:25:54 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-11 04:25:54 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-11 04:25:54 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-11 04:25:54 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-11 04:25:54 (7698) [INFO] 
* 2024-10-11 04:25:59 (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 04:25:59 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-11 04:25:59 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-11 04:26:00 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/J69rUUOrpc/ea_profile.json
* 2024-10-11 04:26: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/J69rUUOrpc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-11 04:26:03 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-12 04:26:30 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-12 04:26:30 (9031) [INFO] Script is up to date.
* 2024-10-12 04:26:31 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-12 04:26:31 (7668) [INFO] 
* 2024-10-12 04:26:35 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-12 04:26:35 (7668) [INFO] 
* 2024-10-12 04:26:42 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-12 04:26:42 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-12 04:26:42 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-12 04:26:45 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-12 04:26:45 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-12 04:26:45 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-12 04:26:45 (7668) [INFO] 
* 2024-10-12 04:26:45 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-12 04:26:45 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-12 04:26:45 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-12 04:26:45 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-12 04:26:45 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-12 04:26:45 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-12 04:26:45 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-12 04:26:45 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-12 04:26:45 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-12 04:26:45 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-12 04:26:45 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-12 04:26:45 (7698) [INFO] 
* 2024-10-12 04:26:50 (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 04:26:50 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-12 04:26:50 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-12 04:26:51 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fFgN2aelZF/ea_profile.json
* 2024-10-12 04:26:54 (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/fFgN2aelZF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-12 04:26:54 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-13 04:26:29 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-13 04:26:29 (9031) [INFO] Script is up to date.
* 2024-10-13 04:26:30 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-13 04:26:30 (7668) [INFO] 
* 2024-10-13 04:26:33 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-13 04:26:33 (7668) [INFO] 
* 2024-10-13 04:26:39 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-13 04:26:39 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-13 04:26:39 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-13 04:26:41 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-13 04:26:41 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-13 04:26:41 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-13 04:26:41 (7668) [INFO] 
* 2024-10-13 04:26:41 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-13 04:26:41 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-13 04:26:41 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-13 04:26:41 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-13 04:26:41 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-13 04:26:41 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-13 04:26:41 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-13 04:26:41 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-13 04:26:41 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-13 04:26:41 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-13 04:26:41 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-13 04:26:41 (7698) [INFO] 
* 2024-10-13 04:26:45 (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 04:26:45 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-13 04:26:46 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-13 04:26:46 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jZzdpKHN04/ea_profile.json
* 2024-10-13 04:26: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/jZzdpKHN04/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-13 04:26:48 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-14 04:25:34 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-14 04:25:34 (9031) [INFO] Script is up to date.
* 2024-10-14 04:25:35 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-14 04:25:35 (7668) [INFO] 
* 2024-10-14 04:25:38 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-14 04:25:38 (7668) [INFO] 
* 2024-10-14 04:25:45 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-14 04:25:45 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-14 04:25:45 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-14 04:25:47 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-14 04:25:47 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-14 04:25:47 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-14 04:25:47 (7668) [INFO] 
* 2024-10-14 04:25:47 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-14 04:25:48 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-14 04:25:48 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-14 04:25:48 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-14 04:25:48 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-14 04:25:48 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-14 04:25:48 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-14 04:25:48 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-14 04:25:48 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-14 04:25:48 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-14 04:25:48 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-14 04:25:48 (7698) [INFO] 
* 2024-10-14 04:25:52 (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 04:25:52 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-14 04:25:52 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-14 04:25:53 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JNJA5tioPL/ea_profile.json
* 2024-10-14 04:25:54 (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/JNJA5tioPL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-14 04:25:54 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-15 04:25:34 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-15 04:25:34 (9031) [INFO] Script is up to date.
* 2024-10-15 04:25:35 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-15 04:25:35 (7668) [INFO] 
* 2024-10-15 04:25:38 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-15 04:25:38 (7668) [INFO] 
* 2024-10-15 04:25:44 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-15 04:25:44 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-15 04:25:44 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-15 04:25:47 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-15 04:25:47 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-15 04:25:47 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-15 04:25:47 (7668) [INFO] 
* 2024-10-15 04:25:47 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-15 04:25:47 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-15 04:25:47 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-15 04:25:47 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-15 04:25:47 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-15 04:25:47 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-15 04:25:47 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-15 04:25:47 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-15 04:25:47 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-15 04:25:47 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-15 04:25:47 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-15 04:25:47 (7698) [INFO] 
* 2024-10-15 04:25:52 (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 04:25:52 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-15 04:25:52 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-15 04:25:54 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uqrowIfiw7/ea_profile.json
* 2024-10-15 04:25: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/uqrowIfiw7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-15 04:25:56 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-16 04:26:07 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-16 04:26:07 (9031) [INFO] Script is up to date.
* 2024-10-16 04:26:10 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-16 04:26:10 (7668) [INFO] 
* 2024-10-16 04:26:15 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-16 04:26:15 (7668) [INFO] 
* 2024-10-16 04:26:22 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-16 04:26:22 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-16 04:26:22 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-16 04:26:24 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-16 04:26:24 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-16 04:26:24 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-16 04:26:24 (7668) [INFO] 
* 2024-10-16 04:26:24 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-16 04:26:25 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-16 04:26:25 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-16 04:26:25 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-16 04:26:25 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-16 04:26:25 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-16 04:26:25 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-16 04:26:25 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-16 04:26:25 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-16 04:26:25 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-16 04:26:25 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-16 04:26:25 (7698) [INFO] 
* 2024-10-16 04:26: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-16 04:26:30 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-16 04:26:30 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-16 04:26:31 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ykey8ES0da/ea_profile.json
* 2024-10-16 04:26:33 (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/ykey8ES0da/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-16 04:26:33 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-17 04:25:38 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-17 04:25:38 (9031) [INFO] Script is up to date.
* 2024-10-17 04:25:39 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-17 04:25:39 (7668) [INFO] 
* 2024-10-17 04:25:42 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-17 04:25:42 (7668) [INFO] 
* 2024-10-17 04:25:48 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-17 04:25:48 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-17 04:25:48 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-17 04:25:50 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-17 04:25:50 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-17 04:25:50 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-17 04:25:50 (7668) [INFO] 
* 2024-10-17 04:25:50 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-17 04:25:50 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-17 04:25:50 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-17 04:25:50 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-17 04:25:50 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-17 04:25:50 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-17 04:25:50 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-17 04:25:50 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-17 04:25:50 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-17 04:25:50 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-17 04:25:50 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-17 04:25:50 (7698) [INFO] 
* 2024-10-17 04:25: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-10-17 04:25:54 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-17 04:25:55 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-17 04:25:55 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/R33dG5ttkv/ea_profile.json
* 2024-10-17 04:25: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/R33dG5ttkv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-17 04:25:57 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-18 04:26:38 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-18 04:26:38 (9031) [INFO] Script is up to date.
* 2024-10-18 04:26:40 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-18 04:26:40 (7668) [INFO] 
* 2024-10-18 04:26:48 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-18 04:26:48 (7668) [INFO] 
* 2024-10-18 04:26:55 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-18 04:26:55 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-18 04:26:55 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-18 04:26:58 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-18 04:26:58 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-18 04:26:58 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-18 04:26:58 (7668) [INFO] 
* 2024-10-18 04:26:58 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-18 04:26:58 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-18 04:26:58 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-18 04:26:58 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-18 04:26:58 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-18 04:26:58 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-18 04:26:58 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-18 04:26:58 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-18 04:26:58 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-18 04:26:58 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-18 04:26:58 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-18 04:26:58 (7698) [INFO] 
* 2024-10-18 04:27:04 (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 04:27:04 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-18 04:27:04 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-18 04:27:05 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/S7G1C3CePe/ea_profile.json
* 2024-10-18 04:27:08 (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/S7G1C3CePe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-18 04:27:08 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-19 04:26:33 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-19 04:26:33 (9031) [INFO] Script is up to date.
* 2024-10-19 04:26:35 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-19 04:26:35 (7668) [INFO] 
* 2024-10-19 04:26:37 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-19 04:26:37 (7668) [INFO] 
* 2024-10-19 04:26:44 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-19 04:26:44 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-19 04:26:44 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-19 04:26:47 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-19 04:26:47 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-19 04:26:47 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-19 04:26:47 (7668) [INFO] 
* 2024-10-19 04:26:47 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-19 04:26:47 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-19 04:26:47 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-19 04:26:47 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-19 04:26:47 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-19 04:26:47 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-19 04:26:47 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-19 04:26:47 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-19 04:26:47 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-19 04:26:47 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-19 04:26:47 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-19 04:26:47 (7698) [INFO] 
* 2024-10-19 04:26:52 (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 04:26:52 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-19 04:26:52 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-19 04:26:53 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lLuOzcTMAr/ea_profile.json
* 2024-10-19 04:26: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/lLuOzcTMAr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-19 04:26:56 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-20 04:26:20 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-20 04:26:20 (9031) [INFO] Script is up to date.
* 2024-10-20 04:26:22 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-20 04:26:22 (7668) [INFO] 
* 2024-10-20 04:28:42 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-20 04:28:42 (7668) [INFO] 
* 2024-10-20 04:28:49 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-20 04:28:49 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-20 04:28:49 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-20 04:28:51 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-20 04:28:51 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-20 04:28:51 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-20 04:28:51 (7668) [INFO] 
* 2024-10-20 04:28:51 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-20 04:28:51 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-20 04:28:51 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-20 04:28:51 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-20 04:28:51 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-20 04:28:51 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-20 04:28:51 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-20 04:28:51 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-20 04:28:51 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-20 04:28:51 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-20 04:28:51 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-20 04:28:51 (7698) [INFO] 
* 2024-10-20 04:28: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-20 04:28:56 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-20 04:28:56 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-20 04:28:57 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/f9eyP06Onf/ea_profile.json
* 2024-10-20 04:28: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/f9eyP06Onf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-20 04:28:59 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-21 04:25:35 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-21 04:25:35 (9031) [INFO] Script is up to date.
* 2024-10-21 04:25:36 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-21 04:25:36 (7668) [INFO] 
* 2024-10-21 04:25:39 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-21 04:25:39 (7668) [INFO] 
* 2024-10-21 04:25:47 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-21 04:25:47 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-21 04:25:47 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-21 04:25:49 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-21 04:25:49 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-21 04:25:49 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-21 04:25:49 (7668) [INFO] 
* 2024-10-21 04:25:50 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-21 04:25:50 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-21 04:25:50 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-21 04:25:50 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-21 04:25:50 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-21 04:25:50 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-21 04:25:50 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-21 04:25:50 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-21 04:25:50 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-21 04:25:50 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-21 04:25:50 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-21 04:25:50 (7698) [INFO] 
* 2024-10-21 04:25: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 04:25:55 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-21 04:25:55 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-21 04:25:56 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eCya7oULnX/ea_profile.json
* 2024-10-21 04:25: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/eCya7oULnX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-21 04:25:59 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-22 04:25:36 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-22 04:25:36 (9031) [INFO] Script is up to date.
* 2024-10-22 04:25:37 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-22 04:25:37 (7668) [INFO] 
* 2024-10-22 04:25:40 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-22 04:25:40 (7668) [INFO] 
* 2024-10-22 04:25:47 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-22 04:25:47 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-22 04:25:47 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-22 04:25:49 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-22 04:25:49 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-22 04:25:49 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-22 04:25:49 (7668) [INFO] 
* 2024-10-22 04:25:49 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-22 04:25:49 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-22 04:25:49 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-22 04:25:49 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-22 04:25:49 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-22 04:25:49 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-22 04:25:49 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-22 04:25:49 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-22 04:25:49 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-22 04:25:49 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-22 04:25:49 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-22 04:25:49 (7698) [INFO] 
* 2024-10-22 04:25: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-22 04:25:53 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-22 04:25:54 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-22 04:25:54 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5DGczhxNtv/ea_profile.json
* 2024-10-22 04:25: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/5DGczhxNtv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-22 04:25:56 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-23 04:25:38 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-23 04:25:38 (9031) [INFO] Script is up to date.
* 2024-10-23 04:25:39 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-23 04:25:39 (7668) [INFO] 
* 2024-10-23 04:25:43 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-23 04:25:43 (7668) [INFO] 
* 2024-10-23 04:25:50 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-23 04:25:50 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-23 04:25:50 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-23 04:25:51 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-23 04:25:51 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-23 04:25:51 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-23 04:25:51 (7668) [INFO] 
* 2024-10-23 04:25:52 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-23 04:25:52 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-23 04:25:52 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-23 04:25:52 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-23 04:25:52 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-23 04:25:52 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-23 04:25:52 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-23 04:25:52 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-23 04:25:52 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-23 04:25:52 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-23 04:25:52 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-23 04:25:52 (7698) [INFO] 
* 2024-10-23 04:25: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-23 04:25:56 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-23 04:25:56 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-23 04:25:57 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/my1xXaCSGX/ea_profile.json
* 2024-10-23 04:25: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/my1xXaCSGX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-23 04:25:59 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-24 04:25:34 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-24 04:25:34 (9031) [INFO] Script is up to date.
* 2024-10-24 04:25:35 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-24 04:25:35 (7668) [INFO] 
* 2024-10-24 04:25:38 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-24 04:25:38 (7668) [INFO] 
* 2024-10-24 04:25:44 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-24 04:25:44 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-24 04:25:44 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-24 04:25:46 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-24 04:25:46 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-24 04:25:46 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-24 04:25:46 (7668) [INFO] 
* 2024-10-24 04:25:46 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-24 04:25:46 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-24 04:25:46 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-24 04:25:46 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-24 04:25:46 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-24 04:25:46 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-24 04:25:46 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-24 04:25:46 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-24 04:25:46 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-24 04:25:46 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-24 04:25:46 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-24 04:25:46 (7698) [INFO] 
* 2024-10-24 04:25:50 (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 04:25:50 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-24 04:25:51 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-24 04:25:51 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pfZbCOe1af/ea_profile.json
* 2024-10-24 04:25:53 (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/pfZbCOe1af/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-24 04:25:53 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-25 04:26:14 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-25 04:26:14 (9031) [INFO] Script is up to date.
* 2024-10-25 04:26:17 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-25 04:26:17 (7668) [INFO] 
* 2024-10-25 04:26:20 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-25 04:26:20 (7668) [INFO] 
* 2024-10-25 04:26:28 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-25 04:26:28 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-25 04:26:28 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-25 04:26:30 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-25 04:26:30 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-25 04:26:30 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-25 04:26:30 (7668) [INFO] 
* 2024-10-25 04:26:31 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-25 04:26:31 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-25 04:26:31 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-25 04:26:31 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-25 04:26:31 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-25 04:26:31 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-25 04:26:31 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-25 04:26:31 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-25 04:26:31 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-25 04:26:31 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-25 04:26:31 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-25 04:26:31 (7698) [INFO] 
* 2024-10-25 04:26: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 04:26:36 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-25 04:26:36 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-25 04:26:37 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IJJKOJvWRU/ea_profile.json
* 2024-10-25 04:26:39 (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/IJJKOJvWRU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-25 04:26:39 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-26 04:26:27 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-26 04:26:27 (9031) [INFO] Script is up to date.
* 2024-10-26 04:26:29 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-26 04:26:29 (7668) [INFO] 
* 2024-10-26 04:26:32 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-26 04:26:32 (7668) [INFO] 
* 2024-10-26 04:26:41 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-26 04:26:41 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-26 04:26:41 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-26 04:26:42 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-26 04:26:42 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-26 04:26:42 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-26 04:26:42 (7668) [INFO] 
* 2024-10-26 04:26:43 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-26 04:26:43 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-26 04:26:43 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-26 04:26:43 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-26 04:26:43 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-26 04:26:43 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-26 04:26:43 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-26 04:26:43 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-26 04:26:43 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-26 04:26:43 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-26 04:26:43 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-26 04:26:43 (7698) [INFO] 
* 2024-10-26 04:26:47 (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 04:26:47 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-26 04:26:48 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-26 04:26:48 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zTZwypWMvr/ea_profile.json
* 2024-10-26 04:26:50 (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/zTZwypWMvr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-26 04:26:50 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-27 04:26:27 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-27 04:26:27 (9031) [INFO] Script is up to date.
* 2024-10-27 04:26:29 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-27 04:26:29 (7668) [INFO] 
* 2024-10-27 04:26:33 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-27 04:26:33 (7668) [INFO] 
* 2024-10-27 04:26:40 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-27 04:26:40 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-27 04:26:40 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-27 04:26:43 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-27 04:26:43 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-27 04:26:43 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-27 04:26:43 (7668) [INFO] 
* 2024-10-27 04:26:43 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-27 04:26:43 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-27 04:26:43 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-27 04:26:43 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-27 04:26:43 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-27 04:26:43 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-27 04:26:43 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-27 04:26:43 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-27 04:26:43 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-27 04:26:43 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-27 04:26:43 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-27 04:26:43 (7698) [INFO] 
* 2024-10-27 04:26:48 (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-27 04:26:48 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-27 04:26:49 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-27 04:26:50 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5XTO4ivMx2/ea_profile.json
* 2024-10-27 04:26:53 (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/5XTO4ivMx2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-27 04:26:53 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-28 04:25:36 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-28 04:25:36 (9031) [INFO] Script is up to date.
* 2024-10-28 04:25:39 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-28 04:25:39 (7668) [INFO] 
* 2024-10-28 04:25:42 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-28 04:25:42 (7668) [INFO] 
* 2024-10-28 04:25:49 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-28 04:25:49 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-28 04:25:49 (2136) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-28 04:25:51 (1995) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-28 04:25:51 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-28 04:25:51 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-28 04:25:51 (7668) [INFO] 
* 2024-10-28 04:25:52 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-28 04:25:52 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-28 04:25:52 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-28 04:25:52 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-28 04:25:52 (7681) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-28 04:25:52 (7681) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-28 04:25:52 (7681) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-28 04:25:52 (7681) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-28 04:25:52 (7681) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-28 04:25:52 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-28 04:25:52 (7681) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-28 04:25:52 (7698) [INFO] 
* 2024-10-28 04:25: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-28 04:25:57 (2006) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-28 04:25:57 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-28 04:25:58 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/X2LyPy1mRY/ea_profile.json
* 2024-10-28 04:26: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/X2LyPy1mRY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-28 04:26:00 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-29 04:25:35 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-29 04:25:35 (9014) [INFO] Newer version of script found. Downloading.
* 2024-10-29 04:25:37 (9023) [INFO] Script update to version 56 successful.
* 2024-10-29 04:25:38 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-29 04:25:38 (7662) [INFO] 
* 2024-10-29 04:25:42 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-10-29 04:25:42 (7662) [INFO] 
* 2024-10-29 04:25:48 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-29 04:25:48 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-29 04:25:48 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-29 04:25:50 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-29 04:25:50 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-29 04:25:50 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-10-29 04:25:50 (7662) [INFO] 
* 2024-10-29 04:25:50 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-29 04:25:50 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-29 04:25:50 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-29 04:25:50 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-29 04:25:50 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-29 04:25:50 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-29 04:25:50 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-29 04:25:50 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-29 04:25:50 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-29 04:25:50 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-10-29 04:25:50 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-29 04:25:50 (7692) [INFO] 
* 2024-10-29 04:25:54 (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 04:25:54 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-29 04:25:55 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-29 04:25:56 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LA9T9HQQgl/ea_profile.json
* 2024-10-29 04:25:57 (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/LA9T9HQQgl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-29 04:25:57 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-30 04:25:41 (8998) [INFO] Self-update of script version 56 requested.
* 2024-10-30 04:25:41 (9020) [INFO] Script is up to date.
* 2024-10-30 04:25:42 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-30 04:25:42 (7662) [INFO] 
* 2024-10-30 04:25:45 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-10-30 04:25:45 (7662) [INFO] 
* 2024-10-30 04:25:52 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-30 04:25:52 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-30 04:25:52 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-30 04:25:53 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-30 04:25:53 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-30 04:25:53 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-10-30 04:25:53 (7662) [INFO] 
* 2024-10-30 04:25:54 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-30 04:25:54 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-30 04:25:54 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-30 04:25:54 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-30 04:25:54 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-30 04:25:54 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-30 04:25:54 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-30 04:25:54 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-30 04:25:54 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-30 04:25:54 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-10-30 04:25:54 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-30 04:25:54 (7692) [INFO] 
* 2024-10-30 04:25:59 (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 04:25:59 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-30 04:26:00 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-30 04:26:01 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jrOYSTI1aR/ea_profile.json
* 2024-10-30 04:26: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/jrOYSTI1aR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-30 04:26:03 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-31 04:25:34 (8998) [INFO] Self-update of script version 56 requested.
* 2024-10-31 04:25:34 (9020) [INFO] Script is up to date.
* 2024-10-31 04:25:35 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-31 04:25:35 (7662) [INFO] 
* 2024-10-31 04:25:38 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-10-31 04:25:38 (7662) [INFO] 
* 2024-10-31 04:25:45 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-10-31 04:25:45 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-10-31 04:25:45 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-10-31 04:25:54 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-31 04:25:54 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-31 04:25:54 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-10-31 04:25:54 (7662) [INFO] 
* 2024-10-31 04:25:54 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-31 04:25:54 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-10-31 04:25:54 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-31 04:25:54 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-31 04:25:54 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-10-31 04:25:54 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-10-31 04:25:54 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-10-31 04:25:54 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-10-31 04:25:54 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-10-31 04:25:54 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-10-31 04:25:54 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-10-31 04:25:54 (7692) [INFO] 
* 2024-10-31 04:26: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-10-31 04:26:08 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-31 04:26:08 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-31 04:26:09 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6ccVfPno47/ea_profile.json
* 2024-10-31 04:26:16 (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/6ccVfPno47/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-31 04:26:16 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-01 04:28:51 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-01 04:28:51 (9020) [INFO] Script is up to date.
* 2024-11-01 04:28:54 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-01 04:28:54 (7662) [INFO] 
* 2024-11-01 04:28:58 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-01 04:28:58 (7662) [INFO] 
* 2024-11-01 04:29:06 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-01 04:29:06 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-01 04:29:06 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-01 04:29:26 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-01 04:29:26 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-01 04:29:26 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-01 04:29:26 (7662) [INFO] 
* 2024-11-01 04:29:26 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-01 04:29:26 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-01 04:29:26 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-01 04:29:26 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-01 04:29:26 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-01 04:29:26 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-01 04:29:26 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-01 04:29:26 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-01 04:29:26 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-01 04:29:26 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-01 04:29:26 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-01 04:29:26 (7692) [INFO] 
* 2024-11-01 04:29:41 (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 04:29:41 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-01 04:29:42 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-01 04:29:42 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y5tjPHMv7p/ea_profile.json
* 2024-11-01 04:29: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/Y5tjPHMv7p/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-01 04:29:46 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-02 04:26:26 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-02 04:26:26 (9020) [INFO] Script is up to date.
* 2024-11-02 04:26:28 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-02 04:26:28 (7662) [INFO] 
* 2024-11-02 04:26:30 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-02 04:26:30 (7662) [INFO] 
* 2024-11-02 04:26:37 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-02 04:26:37 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-02 04:26:37 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-02 04:26:39 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-02 04:26:39 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-02 04:26:39 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-02 04:26:39 (7662) [INFO] 
* 2024-11-02 04:26:39 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-02 04:26:39 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-02 04:26:39 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-02 04:26:39 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-02 04:26:39 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-02 04:26:39 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-02 04:26:39 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-02 04:26:39 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-02 04:26:39 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-02 04:26:39 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-02 04:26:39 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-02 04:26:39 (7692) [INFO] 
* 2024-11-02 04:26:43 (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 04:26:43 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-02 04:26:43 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-02 04:26:44 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AHqE5c9weJ/ea_profile.json
* 2024-11-02 04:26: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/AHqE5c9weJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-02 04:26:46 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-03 04:26:25 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-03 04:26:26 (9020) [INFO] Script is up to date.
* 2024-11-03 04:26:27 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-03 04:26:27 (7662) [INFO] 
* 2024-11-03 04:26:29 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-03 04:26:29 (7662) [INFO] 
* 2024-11-03 04:26:36 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-03 04:26:36 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-03 04:26:36 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-03 04:26:39 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-03 04:26:39 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-03 04:26:39 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-03 04:26:39 (7662) [INFO] 
* 2024-11-03 04:26:39 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-03 04:26:39 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-03 04:26:39 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-03 04:26:39 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-03 04:26:39 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-03 04:26:39 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-03 04:26:39 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-03 04:26:39 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-03 04:26:39 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-03 04:26:39 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-03 04:26:39 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-03 04:26:40 (7692) [INFO] 
* 2024-11-03 04:26:45 (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 04:26:45 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-03 04:26:45 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-03 04:26:46 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/P5X3zs82Jb/ea_profile.json
* 2024-11-03 04:26:48 (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/P5X3zs82Jb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-03 04:26:48 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-04 04:25:39 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-04 04:25:39 (9020) [INFO] Script is up to date.
* 2024-11-04 04:25:40 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-04 04:25:40 (7662) [INFO] 
* 2024-11-04 04:25:43 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-04 04:25:43 (7662) [INFO] 
* 2024-11-04 04:25:48 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-04 04:25:48 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-04 04:25:48 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-04 04:25:50 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-04 04:25:50 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-04 04:25:50 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-04 04:25:50 (7662) [INFO] 
* 2024-11-04 04:25:50 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-04 04:25:50 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-04 04:25:50 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-04 04:25:50 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-04 04:25:50 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-04 04:25:50 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-04 04:25:50 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-04 04:25:50 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-04 04:25:50 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-04 04:25:50 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-04 04:25:50 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-04 04:25:51 (7692) [INFO] 
* 2024-11-04 04:25:55 (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 04:25:55 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-04 04:25:55 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-04 04:25:56 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IcGjtj9c7J/ea_profile.json
* 2024-11-04 04:25:57 (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/IcGjtj9c7J/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-04 04:25:57 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-05 04:26:28 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-05 04:26:28 (9020) [INFO] Script is up to date.
* 2024-11-05 04:26:29 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-05 04:26:29 (7662) [INFO] 
* 2024-11-05 04:26:32 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-05 04:26:32 (7662) [INFO] 
* 2024-11-05 04:26:38 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-05 04:26:38 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-05 04:26:38 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-05 04:26:41 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-05 04:26:41 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-05 04:26:41 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-05 04:26:41 (7662) [INFO] 
* 2024-11-05 04:26:41 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-05 04:26:41 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-05 04:26:41 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-05 04:26:41 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-05 04:26:41 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-05 04:26:41 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-05 04:26:41 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-05 04:26:41 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-05 04:26:41 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-05 04:26:41 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-05 04:26:41 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-05 04:26:41 (7692) [INFO] 
* 2024-11-05 04:26:45 (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 04:26:45 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-05 04:26:46 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-05 04:26:46 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XWPUqJ5Lwg/ea_profile.json
* 2024-11-05 04:26:49 (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/XWPUqJ5Lwg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-05 04:26:49 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-06 04:25:35 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-06 04:25:35 (9020) [INFO] Script is up to date.
* 2024-11-06 04:25:36 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-06 04:25:36 (7662) [INFO] 
* 2024-11-06 04:25:38 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-06 04:25:38 (7662) [INFO] 
* 2024-11-06 04:25:45 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-06 04:25:45 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-06 04:25:45 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-06 04:25:47 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-06 04:25:47 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-06 04:25:47 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-06 04:25:47 (7662) [INFO] 
* 2024-11-06 04:25:48 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-06 04:25:48 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-06 04:25:48 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-06 04:25:48 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-06 04:25:48 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-06 04:25:48 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-06 04:25:48 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-06 04:25:48 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-06 04:25:48 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-06 04:25:48 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-06 04:25:48 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-06 04:25:48 (7692) [INFO] 
* 2024-11-06 04:25:52 (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 04:25:52 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-06 04:25:52 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-06 04:25:53 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oytzHXm8cB/ea_profile.json
* 2024-11-06 04:25:55 (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/oytzHXm8cB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-06 04:25:55 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-07 04:25:34 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-07 04:25:34 (9020) [INFO] Script is up to date.
* 2024-11-07 04:25:35 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-07 04:25:35 (7662) [INFO] 
* 2024-11-07 04:25:37 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-07 04:25:37 (7662) [INFO] 
* 2024-11-07 04:25:44 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-07 04:25:44 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-07 04:25:44 (5597) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-07 04:25:46 (5456) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-07 04:25:46 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-07 04:25:46 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-07 04:25:46 (7662) [INFO] 
* 2024-11-07 04:25:47 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-07 04:25:47 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-07 04:25:47 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-07 04:25:47 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-07 04:25:47 (7675) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-07 04:25:47 (7675) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-07 04:25:47 (7675) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-07 04:25:47 (7675) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-07 04:25:47 (7675) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-07 04:25:47 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-07 04:25:47 (7675) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-07 04:25:47 (7692) [INFO] 
* 2024-11-07 04:25:51 (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 04:25:51 (5467) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-07 04:25:51 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-07 04:25:52 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GPwiZgyhKM/ea_profile.json
* 2024-11-07 04:25:54 (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/GPwiZgyhKM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-07 04:25:54 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-08 04:25:34 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-08 04:25:35 (9003) [INFO] Newer version of script found. Downloading.
* 2024-11-08 04:25:35 (9012) [INFO] Script update to version 57 successful.
* 2024-11-08 04:25:36 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-08 04:25:36 (8441) [INFO] 
* 2024-11-08 04:25:37 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-08 04:25:37 (8441) [INFO] 
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-08 04:27:20 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 04:27:20 (8471) [INFO] 
* 2024-11-08 04:27:20 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-08 04:27:20 (8441) [INFO] 
* 2024-11-08 04:27:27 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-08 04:27:27 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-08 04:27:27 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-08 04:27:27 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-08 04:27:27 (8441) [INFO] 
* 2024-11-08 04:27:27 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 04:27:27 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-08 04:27:28 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-08 04:27:28 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-08 04:27:28 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-08 04:27:28 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-08 04:27:28 (8454) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-08 04:27:29 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 04:27:29 (8454) [INFO] Trying other mirror.
* 2024-11-08 04:27:29 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-08 04:27:29 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-08 04:27:29 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-08 04:27:29 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-08 04:27:29 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-08 04:27:29 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-08 04:27:29 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-08 04:27:29 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-08 04:27:29 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-08 04:27:29 (8454) [INFO]         or
* 2024-11-08 04:27:29 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-08 04:27:29 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-08 04:27:29 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-08 04:27:29 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-08 04:27:29 (8454) [INFO]         compromise:
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-08 04:27:29 (8454) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-08 04:27:29 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 04:27:29 (8471) [INFO] 
* 2024-11-08 04:27:29 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 04:27:29 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-08 04:27:29 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-08 04:27:29 (8441) [INFO] 
* 2024-11-08 04:27:29 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 04:27:29 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-08 04:27:29 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-08 04:27:29 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-08 04:27:29 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-08 04:27:29 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-08 04:27:29 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-08 04:27:29 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-08 04:27:29 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-08 04:27:29 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-08 04:27:29 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-08 04:27:29 (8471) [INFO] 
* 2024-11-08 04:27:29 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-08 04:27:29 (8441) [INFO] 
* 2024-11-08 04:27:30 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 04:27:30 (8454) [INFO] Determining fastest mirrors
* 2024-11-08 04:27:35 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-08 04:27:35 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-08 04:27:35 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-08 04:27:35 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-08 04:27:35 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-08 04:27:36 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 04:27:36 (8454) [INFO] Trying other mirror.
* 2024-11-08 04:27:36 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-08 04:27:36 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-08 04:27:36 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-08 04:27:36 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-08 04:27:36 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-08 04:27:36 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-08 04:27:36 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-08 04:27:36 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-08 04:27:36 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-08 04:27:36 (8454) [INFO]         or
* 2024-11-08 04:27:36 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-08 04:27:36 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-08 04:27:36 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-08 04:27:36 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-08 04:27:36 (8454) [INFO]         compromise:
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-08 04:27:36 (8454) [INFO] 
* 2024-11-08 04:27:36 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-08 04:27:36 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 04:27:36 (8471) [INFO] 
* 2024-11-08 04:27:36 (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 04:27:36 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 04:27:36 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-08 04:27:39 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3KxFj4lL2H/ea_profile.json
* 2024-11-08 04:27:41 (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/3KxFj4lL2H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-08 04:27:41 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-09 04:26:24 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-09 04:26:25 (9513) [INFO] Script is up to date.
* 2024-11-09 04:26:26 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-09 04:26:26 (8441) [INFO] 
* 2024-11-09 04:31:34 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-09 04:31:34 (8441) [INFO] 
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-09 04:33:16 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 04:33:16 (8471) [INFO] 
* 2024-11-09 04:33:16 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-09 04:33:16 (8441) [INFO] 
* 2024-11-09 04:33:24 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-09 04:33:24 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-09 04:33:24 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-09 04:33:24 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-09 04:33:24 (8441) [INFO] 
* 2024-11-09 04:33:24 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 04:33:24 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-09 04:33:25 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-09 04:33:25 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-09 04:33:25 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-09 04:33:25 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-09 04:33:25 (8454) [INFO]  * remi-safe: muug.ca
* 2024-11-09 04:33:26 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 04:33:26 (8454) [INFO] Trying other mirror.
* 2024-11-09 04:33:26 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-09 04:33:26 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-09 04:33:26 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-09 04:33:26 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-09 04:33:26 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-09 04:33:26 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-09 04:33:26 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-09 04:33:26 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-09 04:33:26 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-09 04:33:26 (8454) [INFO]         or
* 2024-11-09 04:33:26 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-09 04:33:26 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-09 04:33:26 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-09 04:33:26 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-09 04:33:26 (8454) [INFO]         compromise:
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-09 04:33:26 (8454) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-09 04:33:26 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 04:33:26 (8471) [INFO] 
* 2024-11-09 04:33:26 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 04:33:26 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-09 04:33:26 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-09 04:33:26 (8441) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 04:33:26 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-09 04:33:26 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-09 04:33:26 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-09 04:33:26 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-09 04:33:26 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-09 04:33:26 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-09 04:33:26 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-09 04:33:26 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-09 04:33:26 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-09 04:33:26 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-09 04:33:26 (8471) [INFO] 
* 2024-11-09 04:33:26 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-09 04:33:26 (8441) [INFO] 
* 2024-11-09 04:33:26 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 04:33:27 (8454) [INFO] Determining fastest mirrors
* 2024-11-09 04:33:29 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-09 04:33:29 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-09 04:33:29 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-09 04:33:29 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-09 04:33:29 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-09 04:33:30 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 04:33:30 (8454) [INFO] Trying other mirror.
* 2024-11-09 04:33:30 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-09 04:33:30 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-09 04:33:30 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-09 04:33:30 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-09 04:33:30 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-09 04:33:30 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-09 04:33:30 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-09 04:33:30 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-09 04:33:30 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-09 04:33:30 (8454) [INFO]         or
* 2024-11-09 04:33:30 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-09 04:33:30 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-09 04:33:30 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-09 04:33:30 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-09 04:33:30 (8454) [INFO]         compromise:
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-09 04:33:30 (8454) [INFO] 
* 2024-11-09 04:33:30 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-09 04:33:30 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 04:33:30 (8471) [INFO] 
* 2024-11-09 04:33:30 (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 04:33:30 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 04:33:30 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-09 04:33:31 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6t8L7OdvG_/ea_profile.json
* 2024-11-09 04:33:33 (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/6t8L7OdvG_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-09 04:33:33 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-10 04:26:27 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-10 04:26:27 (9513) [INFO] Script is up to date.
* 2024-11-10 04:26:28 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-10 04:26:28 (8441) [INFO] 
* 2024-11-10 04:26:31 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-10 04:26:31 (8441) [INFO] 
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-10 04:28:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 04:28:17 (8471) [INFO] 
* 2024-11-10 04:28:17 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-10 04:28:17 (8441) [INFO] 
* 2024-11-10 04:28:25 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-10 04:28:25 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-10 04:28:25 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-10 04:28:25 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-10 04:28:25 (8441) [INFO] 
* 2024-11-10 04:28:25 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 04:28:25 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-10 04:28:26 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-10 04:28:26 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-10 04:28:26 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-10 04:28:26 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-10 04:28:26 (8454) [INFO]  * remi-safe: muug.ca
* 2024-11-10 04:28:27 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 04:28:27 (8454) [INFO] Trying other mirror.
* 2024-11-10 04:28:27 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-10 04:28:27 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-10 04:28:27 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-10 04:28:27 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-10 04:28:27 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-10 04:28:27 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-10 04:28:27 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-10 04:28:27 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-10 04:28:27 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-10 04:28:27 (8454) [INFO]         or
* 2024-11-10 04:28:27 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-10 04:28:27 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-10 04:28:27 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-10 04:28:27 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-10 04:28:27 (8454) [INFO]         compromise:
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-10 04:28:27 (8454) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-10 04:28:27 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 04:28:27 (8471) [INFO] 
* 2024-11-10 04:28:27 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 04:28:27 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-10 04:28:27 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-10 04:28:27 (8441) [INFO] 
* 2024-11-10 04:28:27 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 04:28:27 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-10 04:28:27 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-10 04:28:27 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-10 04:28:27 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-10 04:28:27 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-10 04:28:27 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-10 04:28:27 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-10 04:28:27 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-10 04:28:27 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-10 04:28:27 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-10 04:28:28 (8471) [INFO] 
* 2024-11-10 04:28:28 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-10 04:28:28 (8441) [INFO] 
* 2024-11-10 04:28:28 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 04:28:28 (8454) [INFO] Determining fastest mirrors
* 2024-11-10 04:28:33 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-10 04:28:33 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-10 04:28:33 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-10 04:28:33 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-10 04:28:33 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-10 04:28:33 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 04:28:33 (8454) [INFO] Trying other mirror.
* 2024-11-10 04:28:33 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-10 04:28:33 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-10 04:28:33 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-10 04:28:33 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-10 04:28:33 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-10 04:28:33 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-10 04:28:33 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-10 04:28:33 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-10 04:28:33 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-10 04:28:33 (8454) [INFO]         or
* 2024-11-10 04:28:33 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-10 04:28:33 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-10 04:28:33 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-10 04:28:33 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-10 04:28:33 (8454) [INFO]         compromise:
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-10 04:28:33 (8454) [INFO] 
* 2024-11-10 04:28:33 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-10 04:28:33 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 04:28:33 (8471) [INFO] 
* 2024-11-10 04:28:33 (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 04:28:33 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 04:28:34 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-10 04:28:34 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BPUIRZBAcx/ea_profile.json
* 2024-11-10 04:28:37 (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/BPUIRZBAcx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-10 04:28:37 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-11 04:25:40 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-11 04:25:41 (9513) [INFO] Script is up to date.
* 2024-11-11 04:25:42 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-11 04:25:42 (8441) [INFO] 
* 2024-11-11 04:25:45 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-11 04:25:45 (8441) [INFO] 
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-11 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 04:27:36 (8471) [INFO] 
* 2024-11-11 04:27:36 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-11 04:27:36 (8441) [INFO] 
* 2024-11-11 04:27:45 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-11 04:27:45 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-11 04:27:45 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-11 04:27:45 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-11 04:27:45 (8441) [INFO] 
* 2024-11-11 04:27:46 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 04:27:46 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-11 04:27:47 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-11 04:27:47 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-11 04:27:47 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-11 04:27:47 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-11 04:27:47 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-11 04:27:48 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 04:27:48 (8454) [INFO] Trying other mirror.
* 2024-11-11 04:27:48 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-11 04:27:48 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-11 04:27:48 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-11 04:27:48 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-11 04:27:48 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-11 04:27:48 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-11 04:27:48 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-11 04:27:48 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-11 04:27:48 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-11 04:27:48 (8454) [INFO]         or
* 2024-11-11 04:27:48 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-11 04:27:48 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-11 04:27:48 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-11 04:27:48 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-11 04:27:48 (8454) [INFO]         compromise:
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-11 04:27:48 (8454) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-11 04:27:48 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 04:27:48 (8471) [INFO] 
* 2024-11-11 04:27:48 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 04:27:48 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-11 04:27:48 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-11 04:27:48 (8441) [INFO] 
* 2024-11-11 04:27:48 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 04:27:48 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-11 04:27:48 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-11 04:27:48 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-11 04:27:48 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-11 04:27:48 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-11 04:27:48 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-11 04:27:48 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-11 04:27:48 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-11 04:27:48 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-11 04:27:48 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-11 04:27:49 (8471) [INFO] 
* 2024-11-11 04:27:49 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-11 04:27:49 (8441) [INFO] 
* 2024-11-11 04:27:49 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 04:27:49 (8454) [INFO] Determining fastest mirrors
* 2024-11-11 04:27:54 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-11 04:27:54 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-11 04:27:54 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-11 04:27:54 (8454) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-11 04:27:54 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-11 04:27:54 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 04:27:54 (8454) [INFO] Trying other mirror.
* 2024-11-11 04:27:54 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-11 04:27:54 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-11 04:27:54 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-11 04:27:54 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-11 04:27:54 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-11 04:27:54 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-11 04:27:54 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-11 04:27:54 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-11 04:27:54 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-11 04:27:54 (8454) [INFO]         or
* 2024-11-11 04:27:54 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-11 04:27:54 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-11 04:27:54 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-11 04:27:54 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-11 04:27:54 (8454) [INFO]         compromise:
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-11 04:27:54 (8454) [INFO] 
* 2024-11-11 04:27:54 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-11 04:27:54 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 04:27:54 (8471) [INFO] 
* 2024-11-11 04:27: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 04:27:54 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 04:27:55 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-11 04:27:55 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ojD3N__19x/ea_profile.json
* 2024-11-11 04:27: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/ojD3N__19x/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-11 04:27:58 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-12 04:25:37 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-12 04:25:37 (9513) [INFO] Script is up to date.
* 2024-11-12 04:25:38 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-12 04:25:38 (8441) [INFO] 
* 2024-11-12 04:25:41 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-12 04:25:41 (8441) [INFO] 
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-12 04:27:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 04:27:27 (8471) [INFO] 
* 2024-11-12 04:27:27 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-12 04:27:27 (8441) [INFO] 
* 2024-11-12 04:27:36 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-12 04:27:36 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-12 04:27:36 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-12 04:27:36 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-12 04:27:36 (8441) [INFO] 
* 2024-11-12 04:27:36 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 04:27:36 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-12 04:27:36 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-12 04:27:36 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-12 04:27:36 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-12 04:27:36 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-12 04:27:36 (8454) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-12 04:27:37 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 04:27:37 (8454) [INFO] Trying other mirror.
* 2024-11-12 04:27:37 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-12 04:27:37 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-12 04:27:37 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-12 04:27:37 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-12 04:27:37 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-12 04:27:37 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-12 04:27:37 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-12 04:27:37 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-12 04:27:37 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-12 04:27:37 (8454) [INFO]         or
* 2024-11-12 04:27:37 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-12 04:27:37 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-12 04:27:37 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-12 04:27:37 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-12 04:27:37 (8454) [INFO]         compromise:
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-12 04:27:37 (8454) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-12 04:27:37 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 04:27:37 (8471) [INFO] 
* 2024-11-12 04:27:37 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 04:27:37 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-12 04:27:37 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-12 04:27:37 (8441) [INFO] 
* 2024-11-12 04:27:37 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 04:27:38 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-12 04:27:38 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-12 04:27:38 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-12 04:27:38 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-12 04:27:38 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-12 04:27:38 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-12 04:27:38 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-12 04:27:38 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-12 04:27:38 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-12 04:27:38 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-12 04:27:38 (8471) [INFO] 
* 2024-11-12 04:27:38 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-12 04:27:38 (8441) [INFO] 
* 2024-11-12 04:27:38 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 04:27:38 (8454) [INFO] Determining fastest mirrors
* 2024-11-12 04:27:41 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-12 04:27:41 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-12 04:27:41 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-12 04:27:41 (8454) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-12 04:27:41 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-12 04:27:41 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 04:27:41 (8454) [INFO] Trying other mirror.
* 2024-11-12 04:27:41 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-12 04:27:41 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-12 04:27:41 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-12 04:27:41 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-12 04:27:41 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-12 04:27:41 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-12 04:27:41 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-12 04:27:41 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-12 04:27:41 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-12 04:27:41 (8454) [INFO]         or
* 2024-11-12 04:27:41 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-12 04:27:41 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-12 04:27:41 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-12 04:27:41 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-12 04:27:41 (8454) [INFO]         compromise:
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-12 04:27:41 (8454) [INFO] 
* 2024-11-12 04:27:41 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-12 04:27:41 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 04:27:41 (8471) [INFO] 
* 2024-11-12 04:27:41 (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 04:27:41 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 04:27:42 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-12 04:27:42 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pdiuoeNRSt/ea_profile.json
* 2024-11-12 04:27:44 (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/pdiuoeNRSt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-12 04:27:44 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-13 04:30:36 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-13 04:30:36 (9513) [INFO] Script is up to date.
* 2024-11-13 04:30:38 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-13 04:30:38 (8441) [INFO] 
* 2024-11-13 04:30:42 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-13 04:30:42 (8441) [INFO] 
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-13 04:32:28 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 04:32:28 (8471) [INFO] 
* 2024-11-13 04:32:28 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-13 04:32:28 (8441) [INFO] 
* 2024-11-13 04:35:06 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-13 04:35:06 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-13 04:35:06 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-13 04:35:06 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-13 04:35:06 (8441) [INFO] 
* 2024-11-13 04:35:06 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 04:35:06 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-13 04:35:08 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-13 04:35:08 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-13 04:35:08 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-13 04:35:08 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-13 04:35:08 (8454) [INFO]  * remi-safe: muug.ca
* 2024-11-13 04:35:23 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:35:23 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:35:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:35:38 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:35:53 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:35:53 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:36:08 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:36:08 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:36:23 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:36:23 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:36:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:36:38 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:36:53 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:36:53 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:37:08 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:08 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:37:23 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:23 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO]  One of the configured repositories failed (MariaDB103),
* 2024-11-13 04:37:38 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-13 04:37:38 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-13 04:37:38 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-13 04:37:38 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-13 04:37:38 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-13 04:37:38 (8454) [INFO]             yum --disablerepo=MariaDB103 ...
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-13 04:37:38 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-13 04:37:38 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO]             yum-config-manager --disable MariaDB103
* 2024-11-13 04:37:38 (8454) [INFO]         or
* 2024-11-13 04:37:38 (8454) [INFO]             subscription-manager repos --disable=MariaDB103
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-13 04:37:38 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-13 04:37:38 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-13 04:37:38 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-13 04:37:38 (8454) [INFO]         compromise:
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO]             yum-config-manager --save --setopt=MariaDB103.skip_if_unavailable=true
* 2024-11-13 04:37:38 (8454) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO] failure: repodata/repomd.xml from MariaDB103: [Errno 256] No more mirrors to try.
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (8471) [INFO] 
* 2024-11-13 04:37:38 (5507) [WARN] Initial run of "yum makecache" failed: https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.


 One of the configured repositories failed (MariaDB103),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=MariaDB103 ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable MariaDB103
        or
            subscription-manager repos --disable=MariaDB103

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=MariaDB103.skip_if_unavailable=true

failure: repodata/repomd.xml from MariaDB103: [Errno 256] No more mirrors to try.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:38 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-13 04:37:38 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-13 04:37:38 (8441) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 04:37:38 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-13 04:37:38 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-13 04:37:38 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-13 04:37:38 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-13 04:37:38 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-13 04:37:38 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-13 04:37:38 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-13 04:37:38 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-13 04:37:38 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-13 04:37:38 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-13 04:37:38 (8471) [INFO] 
* 2024-11-13 04:37:38 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-13 04:37:38 (8441) [INFO] 
* 2024-11-13 04:37:38 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 04:37:39 (8454) [INFO] Determining fastest mirrors
* 2024-11-13 04:37:42 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-13 04:37:42 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-13 04:37:42 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-13 04:37:42 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-13 04:37:42 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-13 04:37:58 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:37:58 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:38:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:38:13 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:38:28 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:38:28 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:38:43 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:38:43 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:38:58 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:38:58 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:39:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:39:13 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:39:28 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:39:28 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:39:43 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:39:43 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:39:58 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:39:58 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] Trying other mirror.
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO]  One of the configured repositories failed (MariaDB103),
* 2024-11-13 04:40:13 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-13 04:40:13 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-13 04:40:13 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-13 04:40:13 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-13 04:40:13 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-13 04:40:13 (8454) [INFO]             yum --disablerepo=MariaDB103 ...
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-13 04:40:13 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-13 04:40:13 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO]             yum-config-manager --disable MariaDB103
* 2024-11-13 04:40:13 (8454) [INFO]         or
* 2024-11-13 04:40:13 (8454) [INFO]             subscription-manager repos --disable=MariaDB103
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-13 04:40:13 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-13 04:40:13 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-13 04:40:13 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-13 04:40:13 (8454) [INFO]         compromise:
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO]             yum-config-manager --save --setopt=MariaDB103.skip_if_unavailable=true
* 2024-11-13 04:40:13 (8454) [INFO] 
* 2024-11-13 04:40:13 (8454) [INFO] failure: repodata/repomd.xml from MariaDB103: [Errno 256] No more mirrors to try.
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8454) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (8471) [INFO] 
* 2024-11-13 04:40:13 (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 04:40:13 (5518) [ERROR] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.


 One of the configured repositories failed (MariaDB103),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=MariaDB103 ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable MariaDB103
        or
            subscription-manager repos --disable=MariaDB103

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=MariaDB103.skip_if_unavailable=true

failure: repodata/repomd.xml from MariaDB103: [Errno 256] No more mirrors to try.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2024-11-13 04:40:13 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-13 04:40:16 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C1mQCcSy4G/ea_profile.json
* 2024-11-13 04:42: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/C1mQCcSy4G/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-13 04:42:18 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-14 04:25:38 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-14 04:25:38 (9513) [INFO] Script is up to date.
* 2024-11-14 04:25:39 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-14 04:25:39 (8441) [INFO] 
* 2024-11-14 04:25:44 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-14 04:25:44 (8441) [INFO] 
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-14 04:27:31 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 04:27:31 (8471) [INFO] 
* 2024-11-14 04:27:31 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-14 04:27:31 (8441) [INFO] 
* 2024-11-14 04:27:39 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-14 04:27:39 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-14 04:27:39 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-14 04:27:39 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-14 04:27:39 (8441) [INFO] 
* 2024-11-14 04:27:39 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 04:27:40 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-14 04:27:41 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-14 04:27:41 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-14 04:27:41 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-14 04:27:41 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-14 04:27:41 (8454) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-14 04:27:42 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 04:27:42 (8454) [INFO] Trying other mirror.
* 2024-11-14 04:27:42 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-14 04:27:42 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-14 04:27:42 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-14 04:27:42 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-14 04:27:42 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-14 04:27:42 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-14 04:27:42 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-14 04:27:42 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-14 04:27:42 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-14 04:27:42 (8454) [INFO]         or
* 2024-11-14 04:27:42 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-14 04:27:42 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-14 04:27:42 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-14 04:27:42 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-14 04:27:42 (8454) [INFO]         compromise:
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-14 04:27:42 (8454) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-14 04:27:42 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 04:27:42 (8471) [INFO] 
* 2024-11-14 04:27:42 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 04:27:42 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-14 04:27:42 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-14 04:27:42 (8441) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 04:27:42 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-14 04:27:42 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-14 04:27:42 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-14 04:27:42 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-14 04:27:42 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-14 04:27:42 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-14 04:27:42 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-14 04:27:42 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-14 04:27:42 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-14 04:27:42 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-14 04:27:42 (8471) [INFO] 
* 2024-11-14 04:27:42 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-14 04:27:42 (8441) [INFO] 
* 2024-11-14 04:27:42 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 04:27:43 (8454) [INFO] Determining fastest mirrors
* 2024-11-14 04:27:47 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-14 04:27:47 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-14 04:27:47 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-14 04:27:47 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-14 04:27:47 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-14 04:27:47 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 04:27:47 (8454) [INFO] Trying other mirror.
* 2024-11-14 04:27:47 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-14 04:27:47 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-14 04:27:47 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-14 04:27:47 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-14 04:27:47 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-14 04:27:47 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-14 04:27:47 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-14 04:27:47 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-14 04:27:47 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-14 04:27:47 (8454) [INFO]         or
* 2024-11-14 04:27:47 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-14 04:27:47 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-14 04:27:47 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-14 04:27:47 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-14 04:27:47 (8454) [INFO]         compromise:
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-14 04:27:47 (8454) [INFO] 
* 2024-11-14 04:27:47 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-14 04:27:47 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 04:27:47 (8471) [INFO] 
* 2024-11-14 04:27:47 (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 04:27:47 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 04:27:47 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-14 04:27:48 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ve1pKCb7fk/ea_profile.json
* 2024-11-14 04:27:51 (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/Ve1pKCb7fk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-14 04:27:51 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-15 04:25:43 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-15 04:25:43 (9513) [INFO] Script is up to date.
* 2024-11-15 04:25:44 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-15 04:25:44 (8441) [INFO] 
* 2024-11-15 04:25:48 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-15 04:25:48 (8441) [INFO] 
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-15 04:27:36 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 04:27:36 (8471) [INFO] 
* 2024-11-15 04:27:36 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-15 04:27:36 (8441) [INFO] 
* 2024-11-15 04:27:43 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-15 04:27:43 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-15 04:27:43 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-15 04:27:43 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-15 04:27:43 (8441) [INFO] 
* 2024-11-15 04:27:43 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 04:27:43 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-15 04:27:44 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-15 04:27:44 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-15 04:27:44 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-15 04:27:44 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-15 04:27:44 (8454) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-15 04:27:45 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 04:27:45 (8454) [INFO] Trying other mirror.
* 2024-11-15 04:27:45 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-15 04:27:45 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 04:27:45 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 04:27:45 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-15 04:27:45 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-15 04:27:45 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-15 04:27:45 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 04:27:45 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-15 04:27:45 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-15 04:27:45 (8454) [INFO]         or
* 2024-11-15 04:27:45 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 04:27:45 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 04:27:45 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 04:27:45 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 04:27:45 (8454) [INFO]         compromise:
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-15 04:27:45 (8454) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-15 04:27:45 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 04:27:45 (8471) [INFO] 
* 2024-11-15 04:27:45 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 04:27:45 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-15 04:27:45 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-15 04:27:45 (8441) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 04:27:45 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-15 04:27:45 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-15 04:27:45 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-15 04:27:45 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-15 04:27:45 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-15 04:27:45 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-15 04:27:45 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-15 04:27:45 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-15 04:27:45 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-15 04:27:45 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-15 04:27:45 (8471) [INFO] 
* 2024-11-15 04:27:45 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-15 04:27:45 (8441) [INFO] 
* 2024-11-15 04:27:45 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 04:27:45 (8454) [INFO] Determining fastest mirrors
* 2024-11-15 04:27:49 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-15 04:27:49 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-15 04:27:49 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-15 04:27:49 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-15 04:27:49 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-15 04:27:49 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 04:27:49 (8454) [INFO] Trying other mirror.
* 2024-11-15 04:27:49 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-15 04:27:49 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 04:27:49 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 04:27:49 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-15 04:27:49 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-15 04:27:49 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-15 04:27:49 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 04:27:49 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-15 04:27:49 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-15 04:27:49 (8454) [INFO]         or
* 2024-11-15 04:27:49 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 04:27:49 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 04:27:49 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 04:27:49 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 04:27:49 (8454) [INFO]         compromise:
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-15 04:27:49 (8454) [INFO] 
* 2024-11-15 04:27:49 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-15 04:27:49 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 04:27:49 (8471) [INFO] 
* 2024-11-15 04:27:49 (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 04:27:49 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 04:27:49 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-15 04:27:50 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AbERFitZUW/ea_profile.json
* 2024-11-15 04:27:52 (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/AbERFitZUW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-15 04:27:52 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-16 04:26:31 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-16 04:26:31 (9513) [INFO] Script is up to date.
* 2024-11-16 04:26:32 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-16 04:26:32 (8441) [INFO] 
* 2024-11-16 04:26:35 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-16 04:26:35 (8441) [INFO] 
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-16 04:28:25 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 04:28:25 (8471) [INFO] 
* 2024-11-16 04:28:25 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-16 04:28:25 (8441) [INFO] 
* 2024-11-16 04:28:33 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-16 04:28:33 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-16 04:28:33 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-16 04:28:33 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-16 04:28:33 (8441) [INFO] 
* 2024-11-16 04:28:33 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 04:28:33 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-16 04:28:34 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-16 04:28:34 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-16 04:28:34 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-16 04:28:34 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-16 04:28:34 (8454) [INFO]  * remi-safe: muug.ca
* 2024-11-16 04:28:35 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 04:28:35 (8454) [INFO] Trying other mirror.
* 2024-11-16 04:28:35 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-16 04:28:35 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-16 04:28:35 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-16 04:28:35 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-16 04:28:35 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-16 04:28:35 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-16 04:28:35 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-16 04:28:35 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-16 04:28:35 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-16 04:28:35 (8454) [INFO]         or
* 2024-11-16 04:28:35 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-16 04:28:35 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-16 04:28:35 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-16 04:28:35 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-16 04:28:35 (8454) [INFO]         compromise:
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-16 04:28:35 (8454) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-16 04:28:35 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 04:28:35 (8471) [INFO] 
* 2024-11-16 04:28:35 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 04:28:35 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-16 04:28:35 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-16 04:28:35 (8441) [INFO] 
* 2024-11-16 04:28:35 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 04:28:35 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-16 04:28:35 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-16 04:28:35 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-16 04:28:35 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-16 04:28:35 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-16 04:28:35 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-16 04:28:35 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-16 04:28:35 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-16 04:28:36 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-16 04:28:36 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-16 04:28:36 (8471) [INFO] 
* 2024-11-16 04:28:36 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-16 04:28:36 (8441) [INFO] 
* 2024-11-16 04:28:36 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 04:28:36 (8454) [INFO] Determining fastest mirrors
* 2024-11-16 04:28:39 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-16 04:28:39 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-16 04:28:39 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-16 04:28:39 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-16 04:28:39 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-16 04:28:40 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 04:28:40 (8454) [INFO] Trying other mirror.
* 2024-11-16 04:28:40 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-16 04:28:40 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-16 04:28:40 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-16 04:28:40 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-16 04:28:40 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-16 04:28:40 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-16 04:28:40 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-16 04:28:40 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-16 04:28:40 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-16 04:28:40 (8454) [INFO]         or
* 2024-11-16 04:28:40 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-16 04:28:40 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-16 04:28:40 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-16 04:28:40 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-16 04:28:40 (8454) [INFO]         compromise:
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-16 04:28:40 (8454) [INFO] 
* 2024-11-16 04:28:40 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-16 04:28:40 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 04:28:40 (8471) [INFO] 
* 2024-11-16 04:28: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-16 04:28:40 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 04:28:40 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-16 04:28:41 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EoMgKpvP2O/ea_profile.json
* 2024-11-16 04:28:43 (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/EoMgKpvP2O/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-16 04:28:43 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-17 04:26:25 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-17 04:26:26 (9513) [INFO] Script is up to date.
* 2024-11-17 04:26:27 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-17 04:26:27 (8441) [INFO] 
* 2024-11-17 04:26:30 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-17 04:26:30 (8441) [INFO] 
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-17 04:28:21 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 04:28:21 (8471) [INFO] 
* 2024-11-17 04:28:21 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-17 04:28:21 (8441) [INFO] 
* 2024-11-17 04:28:30 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-17 04:28:30 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-17 04:28:30 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-17 04:28:30 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-17 04:28:30 (8441) [INFO] 
* 2024-11-17 04:28:30 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 04:28:30 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-17 04:28:31 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-17 04:28:31 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-17 04:28:31 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-17 04:28:31 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-17 04:28:31 (8454) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-17 04:28:32 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 04:28:32 (8454) [INFO] Trying other mirror.
* 2024-11-17 04:28:32 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-17 04:28:32 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-17 04:28:32 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-17 04:28:32 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-17 04:28:32 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-17 04:28:32 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-17 04:28:32 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-17 04:28:32 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-17 04:28:32 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-17 04:28:32 (8454) [INFO]         or
* 2024-11-17 04:28:32 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-17 04:28:32 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-17 04:28:32 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-17 04:28:32 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-17 04:28:32 (8454) [INFO]         compromise:
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-17 04:28:32 (8454) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-17 04:28:32 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 04:28:32 (8471) [INFO] 
* 2024-11-17 04:28:32 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 04:28:32 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-17 04:28:32 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-17 04:28:32 (8441) [INFO] 
* 2024-11-17 04:28:32 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 04:28:32 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-17 04:28:32 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-17 04:28:32 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-17 04:28:32 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-17 04:28:32 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-17 04:28:32 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-17 04:28:32 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-17 04:28:32 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-17 04:28:32 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-17 04:28:32 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-17 04:28:32 (8471) [INFO] 
* 2024-11-17 04:28:32 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-17 04:28:32 (8441) [INFO] 
* 2024-11-17 04:28:33 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 04:28:33 (8454) [INFO] Determining fastest mirrors
* 2024-11-17 04:28:37 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-17 04:28:37 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-17 04:28:37 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-17 04:28:37 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-17 04:28:37 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-17 04:28:37 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 04:28:37 (8454) [INFO] Trying other mirror.
* 2024-11-17 04:28:37 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-17 04:28:37 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-17 04:28:37 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-17 04:28:37 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-17 04:28:37 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-17 04:28:37 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-17 04:28:37 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-17 04:28:37 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-17 04:28:37 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-17 04:28:37 (8454) [INFO]         or
* 2024-11-17 04:28:37 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-17 04:28:37 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-17 04:28:37 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-17 04:28:37 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-17 04:28:37 (8454) [INFO]         compromise:
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-17 04:28:37 (8454) [INFO] 
* 2024-11-17 04:28:37 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-17 04:28:37 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 04:28:37 (8471) [INFO] 
* 2024-11-17 04:28:37 (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 04:28:37 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 04:28:38 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-17 04:28:38 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3NoVDi5ttR/ea_profile.json
* 2024-11-17 04:28:41 (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/3NoVDi5ttR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-17 04:28:41 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-18 04:25:40 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-18 04:25:40 (9513) [INFO] Script is up to date.
* 2024-11-18 04:25:41 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-18 04:25:41 (8441) [INFO] 
* 2024-11-18 04:25:45 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-18 04:25:45 (8441) [INFO] 
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-18 04:27:35 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 04:27:35 (8471) [INFO] 
* 2024-11-18 04:27:35 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-18 04:27:35 (8441) [INFO] 
* 2024-11-18 04:27:44 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-18 04:27:44 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-18 04:27:44 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-18 04:27:44 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-18 04:27:44 (8441) [INFO] 
* 2024-11-18 04:27:44 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 04:27:44 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-18 04:27:45 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-18 04:27:45 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-18 04:27:45 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-18 04:27:45 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-18 04:27:45 (8454) [INFO]  * remi-safe: muug.ca
* 2024-11-18 04:27:46 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 04:27:46 (8454) [INFO] Trying other mirror.
* 2024-11-18 04:27:46 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-18 04:27:46 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-18 04:27:46 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-18 04:27:46 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-18 04:27:46 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-18 04:27:46 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-18 04:27:46 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-18 04:27:46 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-18 04:27:46 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-18 04:27:46 (8454) [INFO]         or
* 2024-11-18 04:27:46 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-18 04:27:46 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-18 04:27:46 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-18 04:27:46 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-18 04:27:46 (8454) [INFO]         compromise:
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-18 04:27:46 (8454) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-18 04:27:46 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 04:27:46 (8471) [INFO] 
* 2024-11-18 04:27:46 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 04:27:46 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-18 04:27:46 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-18 04:27:46 (8441) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 04:27:46 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-18 04:27:46 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-18 04:27:46 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-18 04:27:46 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-18 04:27:46 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-18 04:27:46 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-18 04:27:46 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-18 04:27:46 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-18 04:27:46 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-18 04:27:46 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-18 04:27:46 (8471) [INFO] 
* 2024-11-18 04:27:46 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-18 04:27:46 (8441) [INFO] 
* 2024-11-18 04:27:46 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 04:27:47 (8454) [INFO] Determining fastest mirrors
* 2024-11-18 04:27:50 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-18 04:27:50 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-18 04:27:50 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-18 04:27:50 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-18 04:27:50 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-18 04:27:50 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 04:27:50 (8454) [INFO] Trying other mirror.
* 2024-11-18 04:27:50 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-18 04:27:50 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-18 04:27:50 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-18 04:27:50 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-18 04:27:50 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-18 04:27:50 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-18 04:27:50 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-18 04:27:50 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-18 04:27:50 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-18 04:27:50 (8454) [INFO]         or
* 2024-11-18 04:27:50 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-18 04:27:50 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-18 04:27:50 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-18 04:27:50 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-18 04:27:50 (8454) [INFO]         compromise:
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-18 04:27:50 (8454) [INFO] 
* 2024-11-18 04:27:50 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-18 04:27:50 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 04:27:51 (8471) [INFO] 
* 2024-11-18 04:27:51 (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 04:27:51 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 04:27:51 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-18 04:27:52 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WFdav9ZCB2/ea_profile.json
* 2024-11-18 04:27:54 (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/WFdav9ZCB2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-18 04:27:54 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-19 04:25:39 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-19 04:25:40 (9513) [INFO] Script is up to date.
* 2024-11-19 04:25:41 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-19 04:25:41 (8441) [INFO] 
* 2024-11-19 04:25:44 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-19 04:25:44 (8441) [INFO] 
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8454) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-19 04:27:30 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 04:27:30 (8471) [INFO] 
* 2024-11-19 04:27:30 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-19 04:27:30 (8441) [INFO] 
* 2024-11-19 04:27:37 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-19 04:27:37 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-19 04:27:37 (5648) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-19 04:27:37 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-19 04:27:37 (8441) [INFO] 
* 2024-11-19 04:27:37 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 04:27:38 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-19 04:27:39 (8454) [INFO]  * EA4: 63.247.64.58
* 2024-11-19 04:27:39 (8454) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-19 04:27:39 (8454) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-19 04:27:39 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-19 04:27:39 (8454) [INFO]  * remi-safe: muug.ca
* 2024-11-19 04:27:39 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 04:27:39 (8454) [INFO] Trying other mirror.
* 2024-11-19 04:27:39 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-19 04:27:39 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-19 04:27:39 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-19 04:27:39 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-19 04:27:39 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-19 04:27:39 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-19 04:27:39 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-19 04:27:39 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-19 04:27:39 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-19 04:27:39 (8454) [INFO]         or
* 2024-11-19 04:27:39 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-19 04:27:39 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-19 04:27:39 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-19 04:27:39 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-19 04:27:39 (8454) [INFO]         compromise:
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-19 04:27:39 (8454) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-19 04:27:39 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 04:27:39 (8471) [INFO] 
* 2024-11-19 04:27:39 (5507) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 04:27:39 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-19 04:27:39 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-19 04:27:39 (8441) [INFO] 
* 2024-11-19 04:27:39 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 04:27:40 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-19 04:27:40 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-19 04:27:40 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-19 04:27:40 (8454) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-19 04:27:40 (8454) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-19 04:27:40 (8454) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-19 04:27:40 (8454) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-19 04:27:40 (8454) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-19 04:27:40 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-19 04:27:40 (8454) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-19 04:27:40 (8471) [INFO] 
* 2024-11-19 04:27:40 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-19 04:27:40 (8441) [INFO] 
* 2024-11-19 04:27:40 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 04:27:40 (8454) [INFO] Determining fastest mirrors
* 2024-11-19 04:27:43 (8454) [INFO]  * EA4: 63.247.64.58
* 2024-11-19 04:27:43 (8454) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-19 04:27:43 (8454) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-19 04:27:43 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-19 04:27:43 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-19 04:27:44 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 04:27:44 (8454) [INFO] Trying other mirror.
* 2024-11-19 04:27:44 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-19 04:27:44 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-19 04:27:44 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-19 04:27:44 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-19 04:27:44 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-19 04:27:44 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-19 04:27:44 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-19 04:27:44 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-19 04:27:44 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-19 04:27:44 (8454) [INFO]         or
* 2024-11-19 04:27:44 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-19 04:27:44 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-19 04:27:44 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-19 04:27:44 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-19 04:27:44 (8454) [INFO]         compromise:
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-19 04:27:44 (8454) [INFO] 
* 2024-11-19 04:27:44 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-19 04:27:44 (8454) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 04:27:44 (8471) [INFO] 
* 2024-11-19 04:27:44 (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 04:27:44 (5518) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 04:27:44 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-19 04:27:45 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fp_YP3YviK/ea_profile.json
* 2024-11-19 04:27: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/fp_YP3YviK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-19 04:27:47 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-20 04:25:35 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-20 04:25:36 (9496) [INFO] Newer version of script found. Downloading.
* 2024-11-20 04:25:36 (9505) [INFO] Script update to version 58 successful.
* 2024-11-20 04:25:38 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-20 04:25:38 (8445) [INFO] 
* 2024-11-20 04:25:40 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-20 04:25:40 (8445) [INFO] 
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-20 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 04:27:29 (8475) [INFO] 
* 2024-11-20 04:27:29 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-20 04:27:29 (8445) [INFO] 
* 2024-11-20 04:27:38 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-20 04:27:38 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-20 04:27:38 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-20 04:27:38 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-20 04:27:38 (8445) [INFO] 
* 2024-11-20 04:27:38 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 04:27:39 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-20 04:27:40 (8458) [INFO]  * EA4: 63.247.64.58
* 2024-11-20 04:27:40 (8458) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-20 04:27:40 (8458) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-20 04:27:40 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-20 04:27:40 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-20 04:27:41 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 04:27:41 (8458) [INFO] Trying other mirror.
* 2024-11-20 04:27:41 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-20 04:27:41 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 04:27:41 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 04:27:41 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-20 04:27:41 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-20 04:27:41 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-20 04:27:41 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 04:27:41 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-20 04:27:41 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-20 04:27:41 (8458) [INFO]         or
* 2024-11-20 04:27:41 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 04:27:41 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 04:27:41 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 04:27:41 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 04:27:41 (8458) [INFO]         compromise:
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-20 04:27:41 (8458) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-20 04:27:41 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 04:27:41 (8475) [INFO] 
* 2024-11-20 04:27:41 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 04:27:41 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-20 04:27:41 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-20 04:27:41 (8445) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 04:27:41 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-20 04:27:41 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-20 04:27:41 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-20 04:27:41 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-20 04:27:41 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-20 04:27:41 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-20 04:27:41 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-20 04:27:41 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-20 04:27:41 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-20 04:27:41 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-20 04:27:41 (8475) [INFO] 
* 2024-11-20 04:27:41 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-20 04:27:41 (8445) [INFO] 
* 2024-11-20 04:27:41 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 04:27:41 (8458) [INFO] Determining fastest mirrors
* 2024-11-20 04:27:45 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-20 04:27:45 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-20 04:27:45 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-20 04:27:45 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-20 04:27:45 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-20 04:27:46 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 04:27:46 (8458) [INFO] Trying other mirror.
* 2024-11-20 04:27:46 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-20 04:27:46 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 04:27:46 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 04:27:46 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-20 04:27:46 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-20 04:27:46 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-20 04:27:46 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 04:27:46 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-20 04:27:46 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-20 04:27:46 (8458) [INFO]         or
* 2024-11-20 04:27:46 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 04:27:46 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 04:27:46 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 04:27:46 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 04:27:46 (8458) [INFO]         compromise:
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-20 04:27:46 (8458) [INFO] 
* 2024-11-20 04:27:46 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-20 04:27:46 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 04:27:46 (8475) [INFO] 
* 2024-11-20 04:27:46 (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 04:27:46 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 04:27:46 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-20 04:27:47 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nIguyXxtKX/ea_profile.json
* 2024-11-20 04:27: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/nIguyXxtKX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-20 04:27:49 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-20 18:15:56 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-20 18:15:56 (9517) [INFO] Script is up to date.
* 2024-11-20 18:15:57 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-20 18:15:57 (8445) [INFO] 
* 2024-11-20 18:16:00 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-20 18:16:00 (8445) [INFO] 
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-20 18:17:51 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 18:17:51 (8475) [INFO] 
* 2024-11-20 18:17:51 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-20 18:17:51 (8445) [INFO] 
* 2024-11-20 18:17:58 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-20 18:17:58 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-20 18:17:58 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-20 18:17:58 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-20 18:17:58 (8445) [INFO] 
* 2024-11-20 18:17:58 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 18:17:58 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-20 18:17:59 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-20 18:17:59 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-20 18:17:59 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-20 18:17:59 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-20 18:17:59 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-20 18:17:59 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 18:17:59 (8458) [INFO] Trying other mirror.
* 2024-11-20 18:17:59 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-20 18:17:59 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 18:17:59 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 18:17:59 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-20 18:17:59 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-20 18:17:59 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-20 18:17:59 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 18:17:59 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-20 18:17:59 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-20 18:17:59 (8458) [INFO]         or
* 2024-11-20 18:17:59 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 18:17:59 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 18:17:59 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 18:17:59 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 18:17:59 (8458) [INFO]         compromise:
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-20 18:17:59 (8458) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-20 18:17:59 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 18:17:59 (8475) [INFO] 
* 2024-11-20 18:17:59 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 18:17:59 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-20 18:17:59 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-20 18:17:59 (8445) [INFO] 
* 2024-11-20 18:17:59 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 18:18:00 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-20 18:18:00 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-20 18:18:00 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-20 18:18:00 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-20 18:18:00 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-20 18:18:00 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-20 18:18:00 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-20 18:18:00 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-20 18:18:00 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-20 18:18:00 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-20 18:18:00 (8475) [INFO] 
* 2024-11-20 18:18:00 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-20 18:18:00 (8445) [INFO] 
* 2024-11-20 18:18:00 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 18:18:00 (8458) [INFO] Determining fastest mirrors
* 2024-11-20 18:18:03 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-20 18:18:03 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-20 18:18:03 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-20 18:18:03 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-20 18:18:03 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-20 18:18:04 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 18:18:04 (8458) [INFO] Trying other mirror.
* 2024-11-20 18:18:04 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-20 18:18:04 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 18:18:04 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 18:18:04 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-20 18:18:04 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-20 18:18:04 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-20 18:18:04 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 18:18:04 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-20 18:18:04 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-20 18:18:04 (8458) [INFO]         or
* 2024-11-20 18:18:04 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 18:18:04 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 18:18:04 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 18:18:04 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 18:18:04 (8458) [INFO]         compromise:
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-20 18:18:04 (8458) [INFO] 
* 2024-11-20 18:18:04 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-20 18:18:04 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 18:18:04 (8475) [INFO] 
* 2024-11-20 18:18:04 (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 18:18:04 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 18:18:04 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-20 18:18:05 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q4u6YjXNJy/ea_profile.json
* 2024-11-20 18:18: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/q4u6YjXNJy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-20 18:18:07 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-21 04:25:33 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-21 04:25:33 (9517) [INFO] Script is up to date.
* 2024-11-21 04:25:35 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-21 04:25:35 (8445) [INFO] 
* 2024-11-21 04:25:37 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-21 04:25:37 (8445) [INFO] 
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-21 04:27:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 04:27:24 (8475) [INFO] 
* 2024-11-21 04:27:24 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-21 04:27:24 (8445) [INFO] 
* 2024-11-21 04:27:32 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-21 04:27:32 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-21 04:27:32 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-21 04:27:32 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 04:27:32 (8445) [INFO] 
* 2024-11-21 04:27:32 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 04:27:32 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-21 04:27:33 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-21 04:27:33 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-21 04:27:33 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-21 04:27:33 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-21 04:27:33 (8458) [INFO]  * remi-safe: muug.ca
* 2024-11-21 04:27:34 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 04:27:34 (8458) [INFO] Trying other mirror.
* 2024-11-21 04:27:34 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-21 04:27:34 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 04:27:34 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 04:27:34 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 04:27:34 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 04:27:34 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 04:27:34 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 04:27:34 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 04:27:34 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-21 04:27:34 (8458) [INFO]         or
* 2024-11-21 04:27:34 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 04:27:34 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 04:27:34 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 04:27:34 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 04:27:34 (8458) [INFO]         compromise:
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-21 04:27:34 (8458) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-21 04:27:34 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 04:27:34 (8475) [INFO] 
* 2024-11-21 04:27:34 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 04:27:34 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-21 04:27:34 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-21 04:27:34 (8445) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 04:27:34 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-21 04:27:34 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-21 04:27:34 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-21 04:27:34 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-21 04:27:34 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-21 04:27:34 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-21 04:27:34 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-21 04:27:34 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-21 04:27:34 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-21 04:27:34 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-21 04:27:34 (8475) [INFO] 
* 2024-11-21 04:27:34 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 04:27:34 (8445) [INFO] 
* 2024-11-21 04:27:34 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 04:27:35 (8458) [INFO] Determining fastest mirrors
* 2024-11-21 04:27:38 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-21 04:27:38 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-21 04:27:38 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-21 04:27:38 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-21 04:27:38 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-21 04:27:38 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 04:27:38 (8458) [INFO] Trying other mirror.
* 2024-11-21 04:27:38 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-21 04:27:38 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 04:27:38 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 04:27:38 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 04:27:38 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 04:27:38 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 04:27:38 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 04:27:38 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 04:27:38 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-21 04:27:38 (8458) [INFO]         or
* 2024-11-21 04:27:38 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 04:27:38 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 04:27:38 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 04:27:38 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 04:27:38 (8458) [INFO]         compromise:
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-21 04:27:38 (8458) [INFO] 
* 2024-11-21 04:27:38 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-21 04:27:38 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 04:27:38 (8475) [INFO] 
* 2024-11-21 04:27:38 (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 04:27:38 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 04:27:39 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-21 04:27:40 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hd6XDxA89t/ea_profile.json
* 2024-11-21 04:27:42 (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/hd6XDxA89t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-21 04:27:42 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-22 04:25:39 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-22 04:25:39 (9517) [INFO] Script is up to date.
* 2024-11-22 04:25:40 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-22 04:25:40 (8445) [INFO] 
* 2024-11-22 04:25:44 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-22 04:25:44 (8445) [INFO] 
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-22 04:27:36 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 04:27:36 (8475) [INFO] 
* 2024-11-22 04:27:36 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-22 04:27:36 (8445) [INFO] 
* 2024-11-22 04:27:46 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-22 04:27:46 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-22 04:27:46 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-22 04:27:46 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-22 04:27:46 (8445) [INFO] 
* 2024-11-22 04:27:46 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 04:27:46 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-22 04:27:48 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-22 04:27:48 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-22 04:27:48 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-22 04:27:48 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-22 04:27:48 (8458) [INFO]  * remi-safe: muug.ca
* 2024-11-22 04:27:48 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 04:27:48 (8458) [INFO] Trying other mirror.
* 2024-11-22 04:27:48 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-22 04:27:48 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 04:27:48 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 04:27:48 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-22 04:27:48 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-22 04:27:48 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-22 04:27:48 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 04:27:48 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-22 04:27:48 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-22 04:27:48 (8458) [INFO]         or
* 2024-11-22 04:27:48 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 04:27:48 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 04:27:48 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 04:27:48 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 04:27:48 (8458) [INFO]         compromise:
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-22 04:27:48 (8458) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-22 04:27:48 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 04:27:48 (8475) [INFO] 
* 2024-11-22 04:27:48 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 04:27:48 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-22 04:27:48 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-22 04:27:48 (8445) [INFO] 
* 2024-11-22 04:27:48 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 04:27:49 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-22 04:27:49 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-22 04:27:49 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-22 04:27:49 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-22 04:27:49 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-22 04:27:49 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-22 04:27:49 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-22 04:27:49 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-22 04:27:49 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-22 04:27:49 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-22 04:27:49 (8475) [INFO] 
* 2024-11-22 04:27:49 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-22 04:27:49 (8445) [INFO] 
* 2024-11-22 04:27:49 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 04:27:49 (8458) [INFO] Determining fastest mirrors
* 2024-11-22 04:27:53 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-22 04:27:53 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-22 04:27:53 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-22 04:27:53 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-22 04:27:53 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-22 04:27:54 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 04:27:54 (8458) [INFO] Trying other mirror.
* 2024-11-22 04:27:54 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-22 04:27:54 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 04:27:54 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 04:27:54 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-22 04:27:54 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-22 04:27:54 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-22 04:27:54 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 04:27:54 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-22 04:27:54 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-22 04:27:54 (8458) [INFO]         or
* 2024-11-22 04:27:54 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 04:27:54 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 04:27:54 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 04:27:54 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 04:27:54 (8458) [INFO]         compromise:
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-22 04:27:54 (8458) [INFO] 
* 2024-11-22 04:27:54 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-22 04:27:54 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 04:27:54 (8475) [INFO] 
* 2024-11-22 04:27:54 (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 04:27:54 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 04:27:54 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-22 04:27:55 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SpTQN7Lo0q/ea_profile.json
* 2024-11-22 04:27:57 (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/SpTQN7Lo0q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-22 04:27:57 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-23 04:26:29 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-23 04:26:29 (9517) [INFO] Script is up to date.
* 2024-11-23 04:26:30 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-23 04:26:30 (8445) [INFO] 
* 2024-11-23 04:26:33 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-23 04:26:33 (8445) [INFO] 
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-23 04:28:24 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 04:28:24 (8475) [INFO] 
* 2024-11-23 04:28:24 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-23 04:28:24 (8445) [INFO] 
* 2024-11-23 04:28:32 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-23 04:28:32 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-23 04:28:32 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-23 04:28:32 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-23 04:28:32 (8445) [INFO] 
* 2024-11-23 04:28:32 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 04:28:32 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-23 04:28:34 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-23 04:28:34 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-23 04:28:34 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-23 04:28:34 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-23 04:28:34 (8458) [INFO]  * remi-safe: muug.ca
* 2024-11-23 04:28:36 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 04:28:36 (8458) [INFO] Trying other mirror.
* 2024-11-23 04:28:36 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-23 04:28:36 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-23 04:28:36 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-23 04:28:36 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-23 04:28:36 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-23 04:28:36 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-23 04:28:36 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-23 04:28:36 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-23 04:28:36 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-23 04:28:36 (8458) [INFO]         or
* 2024-11-23 04:28:36 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-23 04:28:36 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-23 04:28:36 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-23 04:28:36 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-23 04:28:36 (8458) [INFO]         compromise:
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-23 04:28:36 (8458) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-23 04:28:36 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 04:28:36 (8475) [INFO] 
* 2024-11-23 04:28:36 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 04:28:36 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-23 04:28:36 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-23 04:28:36 (8445) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 04:28:36 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-23 04:28:36 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-23 04:28:36 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-23 04:28:36 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-23 04:28:36 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-23 04:28:36 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-23 04:28:36 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-23 04:28:36 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-23 04:28:36 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-23 04:28:36 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-23 04:28:36 (8475) [INFO] 
* 2024-11-23 04:28:36 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-23 04:28:36 (8445) [INFO] 
* 2024-11-23 04:28:36 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 04:28:37 (8458) [INFO] Determining fastest mirrors
* 2024-11-23 04:28:40 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-23 04:28:40 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-23 04:28:40 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-23 04:28:40 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-23 04:28:40 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-23 04:28:41 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 04:28:41 (8458) [INFO] Trying other mirror.
* 2024-11-23 04:28:41 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-23 04:28:41 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-23 04:28:41 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-23 04:28:41 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-23 04:28:41 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-23 04:28:41 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-23 04:28:41 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-23 04:28:41 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-23 04:28:41 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-23 04:28:41 (8458) [INFO]         or
* 2024-11-23 04:28:41 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-23 04:28:41 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-23 04:28:41 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-23 04:28:41 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-23 04:28:41 (8458) [INFO]         compromise:
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-23 04:28:41 (8458) [INFO] 
* 2024-11-23 04:28:41 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-23 04:28:41 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 04:28:41 (8475) [INFO] 
* 2024-11-23 04:28:41 (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 04:28:41 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 04:28:41 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-23 04:28:42 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hQcFziCR9R/ea_profile.json
* 2024-11-23 04:28:44 (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/hQcFziCR9R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-23 04:28:44 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-24 04:26:27 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-24 04:26:27 (9517) [INFO] Script is up to date.
* 2024-11-24 04:26:28 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-24 04:26:28 (8445) [INFO] 
* 2024-11-24 04:26:31 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-24 04:26:31 (8445) [INFO] 
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-24 04:28:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 04:28:22 (8475) [INFO] 
* 2024-11-24 04:28:22 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-24 04:28:22 (8445) [INFO] 
* 2024-11-24 04:28:30 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-24 04:28:30 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-24 04:28:30 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-24 04:28:30 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-24 04:28:30 (8445) [INFO] 
* 2024-11-24 04:28:30 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 04:28:31 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-24 04:28:32 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-24 04:28:32 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-24 04:28:32 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-24 04:28:32 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-24 04:28:32 (8458) [INFO]  * remi-safe: muug.ca
* 2024-11-24 04:28:33 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 04:28:33 (8458) [INFO] Trying other mirror.
* 2024-11-24 04:28:33 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-24 04:28:33 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-24 04:28:33 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-24 04:28:33 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-24 04:28:33 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-24 04:28:33 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-24 04:28:33 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-24 04:28:33 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-24 04:28:33 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-24 04:28:33 (8458) [INFO]         or
* 2024-11-24 04:28:33 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-24 04:28:33 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-24 04:28:33 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-24 04:28:33 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-24 04:28:33 (8458) [INFO]         compromise:
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-24 04:28:33 (8458) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-24 04:28:33 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 04:28:33 (8475) [INFO] 
* 2024-11-24 04:28:33 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 04:28:33 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-24 04:28:33 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-24 04:28:33 (8445) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 04:28:33 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-24 04:28:33 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-24 04:28:33 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-24 04:28:33 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-24 04:28:33 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-24 04:28:33 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-24 04:28:33 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-24 04:28:33 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-24 04:28:33 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-24 04:28:33 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-24 04:28:33 (8475) [INFO] 
* 2024-11-24 04:28:33 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-24 04:28:33 (8445) [INFO] 
* 2024-11-24 04:28:33 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 04:28:33 (8458) [INFO] Determining fastest mirrors
* 2024-11-24 04:28:37 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-24 04:28:37 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-24 04:28:37 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-24 04:28:37 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-24 04:28:37 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-24 04:28:38 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 04:28:38 (8458) [INFO] Trying other mirror.
* 2024-11-24 04:28:38 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-24 04:28:38 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-24 04:28:38 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-24 04:28:38 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-24 04:28:38 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-24 04:28:38 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-24 04:28:38 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-24 04:28:38 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-24 04:28:38 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-24 04:28:38 (8458) [INFO]         or
* 2024-11-24 04:28:38 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-24 04:28:38 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-24 04:28:38 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-24 04:28:38 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-24 04:28:38 (8458) [INFO]         compromise:
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-24 04:28:38 (8458) [INFO] 
* 2024-11-24 04:28:38 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-24 04:28:38 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 04:28:38 (8475) [INFO] 
* 2024-11-24 04:28:38 (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 04:28:38 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 04:28:38 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-24 04:28:39 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yn5ihwJVhX/ea_profile.json
* 2024-11-24 04:28:41 (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/yn5ihwJVhX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-24 04:28:41 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-25 04:25:43 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-25 04:25:43 (9517) [INFO] Script is up to date.
* 2024-11-25 04:25:44 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-25 04:25:44 (8445) [INFO] 
* 2024-11-25 04:27:06 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-25 04:27:06 (8445) [INFO] 
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-25 04:28:55 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 04:28:55 (8475) [INFO] 
* 2024-11-25 04:28:55 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-25 04:28:55 (8445) [INFO] 
* 2024-11-25 04:29:04 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-25 04:29:04 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-25 04:29:04 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-25 04:29:04 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-25 04:29:04 (8445) [INFO] 
* 2024-11-25 04:29:04 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 04:29:04 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-25 04:29:05 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-25 04:29:05 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-25 04:29:05 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-25 04:29:05 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-25 04:29:05 (8458) [INFO]  * remi-safe: muug.ca
* 2024-11-25 04:29:06 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 04:29:06 (8458) [INFO] Trying other mirror.
* 2024-11-25 04:29:06 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-25 04:29:06 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-25 04:29:06 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-25 04:29:06 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-25 04:29:06 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-25 04:29:06 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-25 04:29:06 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-25 04:29:06 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-25 04:29:06 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-25 04:29:06 (8458) [INFO]         or
* 2024-11-25 04:29:06 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-25 04:29:06 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-25 04:29:06 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-25 04:29:06 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-25 04:29:06 (8458) [INFO]         compromise:
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-25 04:29:06 (8458) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-25 04:29:06 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 04:29:06 (8475) [INFO] 
* 2024-11-25 04:29:06 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 04:29:06 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-25 04:29:06 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-25 04:29:06 (8445) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 04:29:06 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-25 04:29:06 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-25 04:29:06 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-25 04:29:06 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-25 04:29:06 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-25 04:29:06 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-25 04:29:06 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-25 04:29:06 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-25 04:29:06 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-25 04:29:06 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-25 04:29:06 (8475) [INFO] 
* 2024-11-25 04:29:06 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-25 04:29:06 (8445) [INFO] 
* 2024-11-25 04:29:06 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 04:29:07 (8458) [INFO] Determining fastest mirrors
* 2024-11-25 04:29:11 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-25 04:29:11 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-25 04:29:11 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-25 04:29:11 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-25 04:29:11 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-25 04:29:12 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 04:29:12 (8458) [INFO] Trying other mirror.
* 2024-11-25 04:29:12 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-25 04:29:12 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-25 04:29:12 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-25 04:29:12 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-25 04:29:12 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-25 04:29:12 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-25 04:29:12 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-25 04:29:12 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-25 04:29:12 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-25 04:29:12 (8458) [INFO]         or
* 2024-11-25 04:29:12 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-25 04:29:12 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-25 04:29:12 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-25 04:29:12 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-25 04:29:12 (8458) [INFO]         compromise:
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-25 04:29:12 (8458) [INFO] 
* 2024-11-25 04:29:12 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-25 04:29:12 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 04:29:12 (8475) [INFO] 
* 2024-11-25 04:29:12 (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 04:29:12 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 04:29:12 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-25 04:29:13 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5GAtzz4FeH/ea_profile.json
* 2024-11-25 04:29: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/5GAtzz4FeH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-25 04:29:15 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-26 04:26:16 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-26 04:26:16 (9517) [INFO] Script is up to date.
* 2024-11-26 04:26:19 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-26 04:26:19 (8445) [INFO] 
* 2024-11-26 04:26:25 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-26 04:26:25 (8445) [INFO] 
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-26 04:28:14 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 04:28:14 (8475) [INFO] 
* 2024-11-26 04:28:14 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-26 04:28:14 (8445) [INFO] 
* 2024-11-26 04:28:28 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-26 04:28:28 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-26 04:28:28 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-26 04:28:28 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-26 04:28:28 (8445) [INFO] 
* 2024-11-26 04:28:28 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-26 04:28:28 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-26 04:28:31 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-26 04:28:31 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-26 04:28:31 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-26 04:28:31 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-26 04:28:31 (8458) [INFO]  * remi-safe: muug.ca
* 2024-11-26 04:28:31 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 04:28:31 (8458) [INFO] Trying other mirror.
* 2024-11-26 04:28:31 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-26 04:28:31 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-26 04:28:31 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-26 04:28:31 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-26 04:28:31 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-26 04:28:31 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-26 04:28:31 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-26 04:28:31 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-26 04:28:31 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-26 04:28:31 (8458) [INFO]         or
* 2024-11-26 04:28:31 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-26 04:28:31 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-26 04:28:31 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-26 04:28:31 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-26 04:28:31 (8458) [INFO]         compromise:
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-26 04:28:31 (8458) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-26 04:28:31 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 04:28:31 (8475) [INFO] 
* 2024-11-26 04:28:31 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 04:28:31 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-26 04:28:31 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-26 04:28:31 (8445) [INFO] 
* 2024-11-26 04:28:31 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-26 04:28:32 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-26 04:28:32 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-26 04:28:32 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-26 04:28:32 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-26 04:28:32 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-26 04:28:32 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-26 04:28:32 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-26 04:28:32 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-26 04:28:32 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-26 04:28:32 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-26 04:28:32 (8475) [INFO] 
* 2024-11-26 04:28:32 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-26 04:28:32 (8445) [INFO] 
* 2024-11-26 04:28:32 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-26 04:28:32 (8458) [INFO] Determining fastest mirrors
* 2024-11-26 04:28:37 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-26 04:28:37 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-26 04:28:37 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-26 04:28:37 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-26 04:28:37 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-26 04:28:38 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 04:28:38 (8458) [INFO] Trying other mirror.
* 2024-11-26 04:28:38 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-26 04:28:38 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-26 04:28:38 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-26 04:28:38 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-26 04:28:38 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-26 04:28:38 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-26 04:28:38 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-26 04:28:38 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-26 04:28:38 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-26 04:28:38 (8458) [INFO]         or
* 2024-11-26 04:28:38 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-26 04:28:38 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-26 04:28:38 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-26 04:28:38 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-26 04:28:38 (8458) [INFO]         compromise:
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-26 04:28:38 (8458) [INFO] 
* 2024-11-26 04:28:38 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-26 04:28:38 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 04:28:38 (8475) [INFO] 
* 2024-11-26 04:28:38 (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 04:28:38 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 04:28:38 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-26 04:28:39 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gt0HRxZONe/ea_profile.json
* 2024-11-26 04:28:42 (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/gt0HRxZONe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-26 04:28:42 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-27 04:25:36 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-27 04:25:36 (9517) [INFO] Script is up to date.
* 2024-11-27 04:25:38 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-27 04:25:38 (8445) [INFO] 
* 2024-11-27 04:25:40 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-27 04:25:40 (8445) [INFO] 
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-27 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 04:27:29 (8475) [INFO] 
* 2024-11-27 04:27:29 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-27 04:27:29 (8445) [INFO] 
* 2024-11-27 04:27:37 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-27 04:27:37 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-27 04:27:37 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-27 04:27:37 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-27 04:27:37 (8445) [INFO] 
* 2024-11-27 04:27:37 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-27 04:27:37 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-27 04:27:39 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-27 04:27:39 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-27 04:27:39 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-27 04:27:39 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-27 04:27:39 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-27 04:27:40 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 04:27:40 (8458) [INFO] Trying other mirror.
* 2024-11-27 04:27:40 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-27 04:27:40 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-27 04:27:40 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-27 04:27:40 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-27 04:27:40 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-27 04:27:40 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-27 04:27:40 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-27 04:27:40 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-27 04:27:40 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-27 04:27:40 (8458) [INFO]         or
* 2024-11-27 04:27:40 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-27 04:27:40 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-27 04:27:40 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-27 04:27:40 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-27 04:27:40 (8458) [INFO]         compromise:
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-27 04:27:40 (8458) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-27 04:27:40 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 04:27:40 (8475) [INFO] 
* 2024-11-27 04:27:40 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 04:27:40 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-27 04:27:40 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-27 04:27:40 (8445) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-27 04:27:40 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-27 04:27:40 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-27 04:27:40 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-27 04:27:40 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-27 04:27:40 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-27 04:27:40 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-27 04:27:40 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-27 04:27:40 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-27 04:27:40 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-27 04:27:40 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-27 04:27:40 (8475) [INFO] 
* 2024-11-27 04:27:40 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-27 04:27:40 (8445) [INFO] 
* 2024-11-27 04:27:40 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-27 04:27:40 (8458) [INFO] Determining fastest mirrors
* 2024-11-27 04:27:46 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-27 04:27:46 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-27 04:27:46 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-27 04:27:46 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-27 04:27:46 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-27 04:27:46 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 04:27:46 (8458) [INFO] Trying other mirror.
* 2024-11-27 04:27:46 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-27 04:27:46 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-27 04:27:46 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-27 04:27:46 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-27 04:27:46 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-27 04:27:46 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-27 04:27:46 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-27 04:27:46 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-27 04:27:46 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-27 04:27:46 (8458) [INFO]         or
* 2024-11-27 04:27:46 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-27 04:27:46 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-27 04:27:46 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-27 04:27:46 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-27 04:27:46 (8458) [INFO]         compromise:
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-27 04:27:46 (8458) [INFO] 
* 2024-11-27 04:27:46 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-27 04:27:46 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 04:27:46 (8475) [INFO] 
* 2024-11-27 04:27:46 (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-27 04:27:46 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 04:27:47 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-27 04:27:47 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kkjMJfGiQP/ea_profile.json
* 2024-11-27 04:27: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/kkjMJfGiQP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-27 04:27:50 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-28 04:25:40 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-28 04:25:40 (9517) [INFO] Script is up to date.
* 2024-11-28 04:25:41 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-28 04:25:41 (8445) [INFO] 
* 2024-11-28 04:25:44 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-28 04:25:44 (8445) [INFO] 
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-28 04:27:34 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 04:27:34 (8475) [INFO] 
* 2024-11-28 04:27:34 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-28 04:27:34 (8445) [INFO] 
* 2024-11-28 04:27:40 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-28 04:27:40 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-28 04:27:40 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-28 04:27:40 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-28 04:27:40 (8445) [INFO] 
* 2024-11-28 04:27:41 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 04:27:41 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-28 04:27:42 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-28 04:27:42 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-28 04:27:42 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-28 04:27:42 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-28 04:27:42 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-28 04:27:43 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 04:27:43 (8458) [INFO] Trying other mirror.
* 2024-11-28 04:27:43 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-28 04:27:43 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-28 04:27:43 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-28 04:27:43 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-28 04:27:43 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-28 04:27:43 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-28 04:27:43 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-28 04:27:43 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-28 04:27:43 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-28 04:27:43 (8458) [INFO]         or
* 2024-11-28 04:27:43 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-28 04:27:43 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-28 04:27:43 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-28 04:27:43 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-28 04:27:43 (8458) [INFO]         compromise:
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-28 04:27:43 (8458) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-28 04:27:43 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 04:27:43 (8475) [INFO] 
* 2024-11-28 04:27:43 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 04:27:43 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-28 04:27:43 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-28 04:27:43 (8445) [INFO] 
* 2024-11-28 04:27:43 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 04:27:43 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-28 04:27:43 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-28 04:27:43 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-28 04:27:43 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-28 04:27:43 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-28 04:27:43 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-28 04:27:43 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-28 04:27:43 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-28 04:27:43 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-28 04:27:43 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-28 04:27:43 (8475) [INFO] 
* 2024-11-28 04:27:43 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-28 04:27:43 (8445) [INFO] 
* 2024-11-28 04:27:44 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 04:27:44 (8458) [INFO] Determining fastest mirrors
* 2024-11-28 04:27:47 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-28 04:27:47 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-28 04:27:47 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-28 04:27:48 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-28 04:27:48 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-28 04:27:48 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 04:27:48 (8458) [INFO] Trying other mirror.
* 2024-11-28 04:27:48 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-28 04:27:48 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-28 04:27:48 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-28 04:27:48 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-28 04:27:48 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-28 04:27:48 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-28 04:27:48 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-28 04:27:48 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-28 04:27:48 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-28 04:27:48 (8458) [INFO]         or
* 2024-11-28 04:27:48 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-28 04:27:48 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-28 04:27:48 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-28 04:27:48 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-28 04:27:48 (8458) [INFO]         compromise:
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-28 04:27:48 (8458) [INFO] 
* 2024-11-28 04:27:48 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-28 04:27:48 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 04:27:48 (8475) [INFO] 
* 2024-11-28 04:27:48 (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 04:27:48 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 04:27:48 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-28 04:27:49 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8fVuaWvl_z/ea_profile.json
* 2024-11-28 04:27:52 (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/8fVuaWvl_z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-28 04:27:52 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-29 04:25:36 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-29 04:25:36 (9517) [INFO] Script is up to date.
* 2024-11-29 04:25:37 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-29 04:25:37 (8445) [INFO] 
* 2024-11-29 04:25:40 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-29 04:25:40 (8445) [INFO] 
* 2024-11-29 04:27:31 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-29 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 04:27:32 (8475) [INFO] 
* 2024-11-29 04:27:32 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-29 04:27:32 (8445) [INFO] 
* 2024-11-29 04:27:39 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-29 04:27:39 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-29 04:27:39 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-29 04:27:39 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-29 04:27:39 (8445) [INFO] 
* 2024-11-29 04:27:39 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 04:27:39 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-29 04:27:40 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-29 04:27:40 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-29 04:27:40 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-29 04:27:40 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-29 04:27:40 (8458) [INFO]  * remi-safe: muug.ca
* 2024-11-29 04:27:41 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 04:27:41 (8458) [INFO] Trying other mirror.
* 2024-11-29 04:27:41 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-29 04:27:41 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 04:27:41 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 04:27:41 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-29 04:27:41 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-29 04:27:41 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-29 04:27:41 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 04:27:41 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-29 04:27:41 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-29 04:27:41 (8458) [INFO]         or
* 2024-11-29 04:27:41 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 04:27:41 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 04:27:41 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 04:27:41 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 04:27:41 (8458) [INFO]         compromise:
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-29 04:27:41 (8458) [INFO] 
* 2024-11-29 04:27:41 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-29 04:27:41 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 04:27:42 (8475) [INFO] 
* 2024-11-29 04:27:42 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 04:27:42 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-29 04:27:42 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-29 04:27:42 (8445) [INFO] 
* 2024-11-29 04:27:42 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 04:27:42 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-29 04:27:42 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-29 04:27:42 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-29 04:27:42 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-29 04:27:42 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-29 04:27:42 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-29 04:27:42 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-29 04:27:42 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-29 04:27:42 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-29 04:27:42 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-29 04:27:42 (8475) [INFO] 
* 2024-11-29 04:27:42 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-29 04:27:42 (8445) [INFO] 
* 2024-11-29 04:27:42 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 04:27:42 (8458) [INFO] Determining fastest mirrors
* 2024-11-29 04:27:46 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-29 04:27:46 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-29 04:27:46 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-29 04:27:46 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-29 04:27:46 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-29 04:27:46 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 04:27:46 (8458) [INFO] Trying other mirror.
* 2024-11-29 04:27:46 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-29 04:27:46 (8458) [INFO] 
* 2024-11-29 04:27:46 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-29 04:27:46 (8458) [INFO] 
* 2024-11-29 04:27:46 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-29 04:27:46 (8458) [INFO] 
* 2024-11-29 04:27:46 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-29 04:27:47 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 04:27:47 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 04:27:47 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 04:27:47 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 04:27:47 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-29 04:27:47 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-29 04:27:47 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-29 04:27:47 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-29 04:27:47 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-29 04:27:47 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 04:27:47 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-29 04:27:47 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-29 04:27:47 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-29 04:27:47 (8458) [INFO]         or
* 2024-11-29 04:27:47 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-29 04:27:47 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 04:27:47 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 04:27:47 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 04:27:47 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 04:27:47 (8458) [INFO]         compromise:
* 2024-11-29 04:27:47 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-29 04:27:47 (8458) [INFO] 
* 2024-11-29 04:27:47 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-29 04:27:47 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 04:27:47 (8475) [INFO] 
* 2024-11-29 04:27:47 (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 04:27:47 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 04:27:47 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-29 04:27:48 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Qtq5qONDnp/ea_profile.json
* 2024-11-29 04:27: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/Qtq5qONDnp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-29 04:27:50 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-30 04:26:25 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-30 04:26:25 (9517) [INFO] Script is up to date.
* 2024-11-30 04:26:26 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-30 04:26:26 (8445) [INFO] 
* 2024-11-30 04:26:29 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-30 04:26:29 (8445) [INFO] 
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-11-30 04:28:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 04:28:18 (8475) [INFO] 
* 2024-11-30 04:28:18 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-30 04:28:18 (8445) [INFO] 
* 2024-11-30 04:28:26 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-11-30 04:28:26 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-11-30 04:28:26 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-11-30 04:28:26 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-30 04:28:26 (8445) [INFO] 
* 2024-11-30 04:28:26 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 04:28:26 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-30 04:28:27 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-30 04:28:27 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-30 04:28:27 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-30 04:28:27 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-30 04:28:27 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-30 04:28:28 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 04:28:28 (8458) [INFO] Trying other mirror.
* 2024-11-30 04:28:28 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-30 04:28:28 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-30 04:28:28 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-30 04:28:28 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-30 04:28:28 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-30 04:28:28 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-30 04:28:28 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-30 04:28:28 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-30 04:28:28 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-30 04:28:28 (8458) [INFO]         or
* 2024-11-30 04:28:28 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-30 04:28:28 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-30 04:28:28 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-30 04:28:28 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-30 04:28:28 (8458) [INFO]         compromise:
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-30 04:28:28 (8458) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-30 04:28:28 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 04:28:28 (8475) [INFO] 
* 2024-11-30 04:28:28 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 04:28:28 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-30 04:28:28 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-30 04:28:28 (8445) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 04:28:28 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-11-30 04:28:28 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-30 04:28:28 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-30 04:28:28 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-11-30 04:28:28 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-11-30 04:28:28 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-11-30 04:28:28 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-11-30 04:28:28 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-11-30 04:28:28 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-30 04:28:28 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-11-30 04:28:28 (8475) [INFO] 
* 2024-11-30 04:28:28 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-30 04:28:28 (8445) [INFO] 
* 2024-11-30 04:28:28 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 04:28:28 (8458) [INFO] Determining fastest mirrors
* 2024-11-30 04:28:32 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-30 04:28:32 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-30 04:28:32 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-30 04:28:32 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-30 04:28:32 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-30 04:28:32 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 04:28:32 (8458) [INFO] Trying other mirror.
* 2024-11-30 04:28:32 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-11-30 04:28:32 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-30 04:28:32 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-30 04:28:32 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-30 04:28:32 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-30 04:28:32 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-30 04:28:32 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-30 04:28:32 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-30 04:28:32 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-30 04:28:32 (8458) [INFO]         or
* 2024-11-30 04:28:32 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-30 04:28:32 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-30 04:28:32 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-30 04:28:32 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-30 04:28:32 (8458) [INFO]         compromise:
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-30 04:28:32 (8458) [INFO] 
* 2024-11-30 04:28:32 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-30 04:28:32 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 04:28:32 (8475) [INFO] 
* 2024-11-30 04:28: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-30 04:28:32 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 04:28:33 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-30 04:28:33 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XoqhxvTB5z/ea_profile.json
* 2024-11-30 04:28:35 (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/XoqhxvTB5z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-30 04:28:35 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-01 04:26:26 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-01 04:26:26 (9517) [INFO] Script is up to date.
* 2024-12-01 04:26:27 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-01 04:26:27 (8445) [INFO] 
* 2024-12-01 04:26:31 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-12-01 04:26:31 (8445) [INFO] 
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-12-01 04:28:20 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 04:28:20 (8475) [INFO] 
* 2024-12-01 04:28:20 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-12-01 04:28:20 (8445) [INFO] 
* 2024-12-01 04:28:28 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-01 04:28:28 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-01 04:28:28 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-01 04:28:29 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-01 04:28:29 (8445) [INFO] 
* 2024-12-01 04:28:29 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 04:28:29 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-01 04:28:30 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-01 04:28:30 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-01 04:28:30 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-01 04:28:30 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-01 04:28:30 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-01 04:28:31 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 04:28:31 (8458) [INFO] Trying other mirror.
* 2024-12-01 04:28:31 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-01 04:28:31 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-01 04:28:31 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-01 04:28:31 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-01 04:28:31 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-01 04:28:31 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-01 04:28:31 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-01 04:28:31 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-01 04:28:31 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-01 04:28:31 (8458) [INFO]         or
* 2024-12-01 04:28:31 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-01 04:28:31 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-01 04:28:31 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-01 04:28:31 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-01 04:28:31 (8458) [INFO]         compromise:
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-01 04:28:31 (8458) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-01 04:28:31 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 04:28:31 (8475) [INFO] 
* 2024-12-01 04:28:31 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 04:28:31 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-01 04:28:31 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-12-01 04:28:31 (8445) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 04:28:31 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-01 04:28:31 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-01 04:28:31 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-01 04:28:31 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-01 04:28:31 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-01 04:28:31 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-01 04:28:31 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-01 04:28:31 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-01 04:28:31 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-12-01 04:28:31 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-01 04:28:31 (8475) [INFO] 
* 2024-12-01 04:28:31 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-01 04:28:31 (8445) [INFO] 
* 2024-12-01 04:28:31 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 04:28:32 (8458) [INFO] Determining fastest mirrors
* 2024-12-01 04:28:35 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-01 04:28:35 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-01 04:28:35 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-01 04:28:35 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-01 04:28:35 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-01 04:28:36 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 04:28:36 (8458) [INFO] Trying other mirror.
* 2024-12-01 04:28:36 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-01 04:28:36 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-01 04:28:36 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-01 04:28:36 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-01 04:28:36 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-01 04:28:36 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-01 04:28:36 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-01 04:28:36 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-01 04:28:36 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-01 04:28:36 (8458) [INFO]         or
* 2024-12-01 04:28:36 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-01 04:28:36 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-01 04:28:36 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-01 04:28:36 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-01 04:28:36 (8458) [INFO]         compromise:
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-01 04:28:36 (8458) [INFO] 
* 2024-12-01 04:28:36 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-01 04:28:36 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 04:28:36 (8475) [INFO] 
* 2024-12-01 04:28:36 (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 04:28:36 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 04:28:36 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-01 04:28:37 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IpNgND9dDS/ea_profile.json
* 2024-12-01 04:28: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/IpNgND9dDS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-01 04:28:40 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-02 04:25:38 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-02 04:25:38 (9517) [INFO] Script is up to date.
* 2024-12-02 04:25:39 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-02 04:25:39 (8445) [INFO] 
* 2024-12-02 04:25:43 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-12-02 04:25:43 (8445) [INFO] 
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-12-02 04:27:32 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 04:27:32 (8475) [INFO] 
* 2024-12-02 04:27:32 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-12-02 04:27:32 (8445) [INFO] 
* 2024-12-02 04:27:38 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-02 04:27:38 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-02 04:27:38 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-02 04:27:38 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-02 04:27:38 (8445) [INFO] 
* 2024-12-02 04:27:39 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-02 04:27:39 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-02 04:27:39 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-02 04:27:39 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-02 04:27:39 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-02 04:27:39 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-02 04:27:39 (8458) [INFO]  * remi-safe: muug.ca
* 2024-12-02 04:27:40 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 04:27:40 (8458) [INFO] Trying other mirror.
* 2024-12-02 04:27:40 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-02 04:27:40 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-02 04:27:40 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-02 04:27:40 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-02 04:27:40 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-02 04:27:40 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-02 04:27:40 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-02 04:27:40 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-02 04:27:40 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-02 04:27:40 (8458) [INFO]         or
* 2024-12-02 04:27:40 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-02 04:27:40 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-02 04:27:40 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-02 04:27:40 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-02 04:27:40 (8458) [INFO]         compromise:
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-02 04:27:40 (8458) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-02 04:27:40 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 04:27:40 (8475) [INFO] 
* 2024-12-02 04:27:40 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 04:27:40 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-02 04:27:40 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-12-02 04:27:40 (8445) [INFO] 
* 2024-12-02 04:27:40 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-02 04:27:40 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-02 04:27:40 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-02 04:27:40 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-02 04:27:40 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-02 04:27:40 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-02 04:27:40 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-02 04:27:40 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-02 04:27:40 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-02 04:27:40 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-12-02 04:27:40 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-02 04:27:40 (8475) [INFO] 
* 2024-12-02 04:27:40 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-02 04:27:40 (8445) [INFO] 
* 2024-12-02 04:27:41 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-02 04:27:41 (8458) [INFO] Determining fastest mirrors
* 2024-12-02 04:27:44 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-02 04:27:44 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-02 04:27:44 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-02 04:27:44 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-02 04:27:44 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-02 04:27:44 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 04:27:44 (8458) [INFO] Trying other mirror.
* 2024-12-02 04:27:44 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-02 04:27:44 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-02 04:27:44 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-02 04:27:44 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-02 04:27:44 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-02 04:27:44 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-02 04:27:44 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-02 04:27:44 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-02 04:27:44 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-02 04:27:44 (8458) [INFO]         or
* 2024-12-02 04:27:44 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-02 04:27:44 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-02 04:27:44 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-02 04:27:44 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-02 04:27:44 (8458) [INFO]         compromise:
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-02 04:27:44 (8458) [INFO] 
* 2024-12-02 04:27:44 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-02 04:27:44 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 04:27:45 (8475) [INFO] 
* 2024-12-02 04:27:45 (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-02 04:27:45 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 04:27:45 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-02 04:27:46 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/H4ad1ThHI4/ea_profile.json
* 2024-12-02 04:27: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/H4ad1ThHI4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-02 04:27:47 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-03 04:25:34 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-03 04:25:34 (9517) [INFO] Script is up to date.
* 2024-12-03 04:25:37 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-03 04:25:37 (8445) [INFO] 
* 2024-12-03 04:25:40 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-12-03 04:25:40 (8445) [INFO] 
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_controlpatri.fysiu_finder_tokens_aggregate
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_corona.spetu_finder_tokens_aggregate
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_enel.spetu_finder_tokens_aggregate
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_fitcult.spetu_finder_tokens_aggregate
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventories
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblockinventorynames
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwares
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_glpiuva.glpi_plugin_fusioninventory_dblocksoftwareversions
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_nexnet.yxd3k_finder_tokens_aggregate
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8458) [INFO] urbanovitalinoad_next.feth0_finder_tokens_aggregate
* 2024-12-03 04:27:29 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 04:27:29 (8475) [INFO] 
* 2024-12-03 04:27:29 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-12-03 04:27:29 (8445) [INFO] 
* 2024-12-03 04:27:42 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-03 04:27:42 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-03 04:27:42 (5651) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-03 04:27:42 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-03 04:27:42 (8445) [INFO] 
* 2024-12-03 04:27:42 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 04:27:42 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-03 04:27:43 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-03 04:27:43 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-03 04:27:43 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-03 04:27:43 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-03 04:27:43 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-03 04:27:44 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 04:27:44 (8458) [INFO] Trying other mirror.
* 2024-12-03 04:27:44 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-03 04:27:44 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-03 04:27:44 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-03 04:27:44 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-03 04:27:44 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-03 04:27:44 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-03 04:27:44 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-03 04:27:44 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-03 04:27:44 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-03 04:27:44 (8458) [INFO]         or
* 2024-12-03 04:27:44 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-03 04:27:44 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-03 04:27:44 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-03 04:27:44 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-03 04:27:44 (8458) [INFO]         compromise:
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-03 04:27:44 (8458) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-03 04:27:44 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 04:27:44 (8475) [INFO] 
* 2024-12-03 04:27:44 (5510) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 04:27:44 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-03 04:27:44 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-12-03 04:27:44 (8445) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 04:27:44 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-03 04:27:44 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-03 04:27:44 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-03 04:27:44 (8458) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-03 04:27:44 (8458) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-03 04:27:44 (8458) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-03 04:27:44 (8458) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-03 04:27:44 (8458) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-03 04:27:44 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-12-03 04:27:44 (8458) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-03 04:27:44 (8475) [INFO] 
* 2024-12-03 04:27:44 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-03 04:27:44 (8445) [INFO] 
* 2024-12-03 04:27:44 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 04:27:44 (8458) [INFO] Determining fastest mirrors
* 2024-12-03 04:27:47 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-03 04:27:47 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-03 04:27:47 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-03 04:27:47 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-03 04:27:47 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-03 04:27:48 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 04:27:48 (8458) [INFO] Trying other mirror.
* 2024-12-03 04:27:48 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-03 04:27:48 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-03 04:27:48 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-03 04:27:48 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-03 04:27:48 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-03 04:27:48 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-03 04:27:48 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-03 04:27:48 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-03 04:27:48 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-03 04:27:48 (8458) [INFO]         or
* 2024-12-03 04:27:48 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-03 04:27:48 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-03 04:27:48 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-03 04:27:48 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-03 04:27:48 (8458) [INFO]         compromise:
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-03 04:27:48 (8458) [INFO] 
* 2024-12-03 04:27:48 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-03 04:27:48 (8458) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 04:27:48 (8475) [INFO] 
* 2024-12-03 04:27:48 (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 04:27:48 (5521) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 04:27:48 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-03 04:27:49 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oSmOxZRzml/ea_profile.json
* 2024-12-03 04:27:51 (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/oSmOxZRzml/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-03 04:27:51 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-04 04:25:34 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-04 04:25:34 (9500) [INFO] Newer version of script found. Downloading.
* 2024-12-04 04:25:35 (9509) [INFO] Script update to version 59 successful.
* 2024-12-04 04:25:36 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-04 04:25:36 (9238) [INFO] 
* 2024-12-04 04:25:38 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-04 04:25:38 (9238) [INFO] 
* 2024-12-04 04:25:46 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-04 04:25:46 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-04 04:25:46 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-04 04:25:46 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-04 04:25:46 (9238) [INFO] 
* 2024-12-04 04:25:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 04:25:47 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-04 04:25:48 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-04 04:25:48 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-04 04:25:48 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-04 04:25:48 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-04 04:25:48 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-04 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 04:25:49 (9251) [INFO] Trying other mirror.
* 2024-12-04 04:25:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-04 04:25:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-04 04:25:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-04 04:25:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-04 04:25:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-04 04:25:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-04 04:25:49 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-04 04:25:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-04 04:25:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-04 04:25:49 (9251) [INFO]         or
* 2024-12-04 04:25:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-04 04:25:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-04 04:25:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-04 04:25:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-04 04:25:49 (9251) [INFO]         compromise:
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-04 04:25:49 (9251) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-04 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 04:25:49 (9268) [INFO] 
* 2024-12-04 04:25:49 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 04:25:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-04 04:25:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-04 04:25:49 (9238) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 04:25:49 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-04 04:25:49 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-04 04:25:49 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-04 04:25:49 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-04 04:25:49 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-04 04:25:49 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-04 04:25:49 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-04 04:25:49 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-04 04:25:49 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-04 04:25:49 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-04 04:25:49 (9268) [INFO] 
* 2024-12-04 04:25:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-04 04:25:49 (9238) [INFO] 
* 2024-12-04 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 04:25:49 (9251) [INFO] Determining fastest mirrors
* 2024-12-04 04:25:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-04 04:25:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-04 04:25:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-04 04:25:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-04 04:25:53 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-04 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 04:25:54 (9251) [INFO] Trying other mirror.
* 2024-12-04 04:25:54 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-04 04:25:54 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-04 04:25:54 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-04 04:25:54 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-04 04:25:54 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-04 04:25:54 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-04 04:25:54 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-04 04:25:54 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-04 04:25:54 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-04 04:25:54 (9251) [INFO]         or
* 2024-12-04 04:25:54 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-04 04:25:54 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-04 04:25:54 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-04 04:25:54 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-04 04:25:54 (9251) [INFO]         compromise:
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-04 04:25:54 (9251) [INFO] 
* 2024-12-04 04:25:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-04 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 04:25:54 (9268) [INFO] 
* 2024-12-04 04:25:54 (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 04:25:54 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 04:25:54 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-04 04:25:55 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hDDVC8VRpV/ea_profile.json
* 2024-12-04 04:25: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/hDDVC8VRpV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-04 04:25:57 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-05 04:25:40 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-05 04:25:40 (10313) [INFO] Script is up to date.
* 2024-12-05 04:25:42 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-05 04:25:42 (9238) [INFO] 
* 2024-12-05 04:25:44 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-05 04:25:44 (9238) [INFO] 
* 2024-12-05 04:25:52 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-05 04:25:52 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-05 04:25:52 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-05 04:25:52 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-05 04:25:52 (9238) [INFO] 
* 2024-12-05 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-05 04:25:52 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-05 04:25:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-05 04:25:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-05 04:25:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-05 04:25:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-05 04:25:53 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-05 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 04:25:54 (9251) [INFO] Trying other mirror.
* 2024-12-05 04:25:54 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-05 04:25:54 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-05 04:25:54 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-05 04:25:54 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-05 04:25:54 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-05 04:25:54 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-05 04:25:54 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-05 04:25:54 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-05 04:25:54 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-05 04:25:54 (9251) [INFO]         or
* 2024-12-05 04:25:54 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-05 04:25:54 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-05 04:25:54 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-05 04:25:54 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-05 04:25:54 (9251) [INFO]         compromise:
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-05 04:25:54 (9251) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-05 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 04:25:54 (9268) [INFO] 
* 2024-12-05 04:25:54 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 04:25:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-05 04:25:54 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-05 04:25:54 (9238) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-05 04:25:54 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-05 04:25:54 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-05 04:25:54 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-05 04:25:54 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-05 04:25:54 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-05 04:25:54 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-05 04:25:54 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-05 04:25:54 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-05 04:25:54 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-05 04:25:54 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-05 04:25:54 (9268) [INFO] 
* 2024-12-05 04:25:54 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-05 04:25:54 (9238) [INFO] 
* 2024-12-05 04:25:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-05 04:25:54 (9251) [INFO] Determining fastest mirrors
* 2024-12-05 04:25:59 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-05 04:25:59 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-05 04:25:59 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-05 04:25:59 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-05 04:25:59 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-05 04:26:00 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 04:26:00 (9251) [INFO] Trying other mirror.
* 2024-12-05 04:26:00 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-05 04:26:00 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-05 04:26:00 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-05 04:26:00 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-05 04:26:00 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-05 04:26:00 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-05 04:26:00 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-05 04:26:00 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-05 04:26:00 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-05 04:26:00 (9251) [INFO]         or
* 2024-12-05 04:26:00 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-05 04:26:00 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-05 04:26:00 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-05 04:26:00 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-05 04:26:00 (9251) [INFO]         compromise:
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-05 04:26:00 (9251) [INFO] 
* 2024-12-05 04:26:00 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-05 04:26:00 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 04:26:00 (9268) [INFO] 
* 2024-12-05 04:26:00 (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 04:26:00 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 04:26:00 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-05 04:26:01 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dY0JPDn_96/ea_profile.json
* 2024-12-05 04:26:03 (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/dY0JPDn_96/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-05 04:26:03 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-06 04:25:38 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-06 04:25:38 (10313) [INFO] Script is up to date.
* 2024-12-06 04:25:39 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-06 04:25:39 (9238) [INFO] 
* 2024-12-06 04:25:42 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-06 04:25:42 (9238) [INFO] 
* 2024-12-06 04:25:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-06 04:25:49 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-06 04:25:49 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-06 04:25:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-06 04:25:49 (9238) [INFO] 
* 2024-12-06 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-06 04:25:50 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-06 04:25:51 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-06 04:25:51 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-06 04:25:51 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-06 04:25:51 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-06 04:25:51 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-06 04:25:52 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 04:25:52 (9251) [INFO] Trying other mirror.
* 2024-12-06 04:25:52 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-06 04:25:52 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-06 04:25:52 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-06 04:25:52 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-06 04:25:52 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-06 04:25:52 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-06 04:25:52 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-06 04:25:52 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-06 04:25:52 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-06 04:25:52 (9251) [INFO]         or
* 2024-12-06 04:25:52 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-06 04:25:52 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-06 04:25:52 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-06 04:25:52 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-06 04:25:52 (9251) [INFO]         compromise:
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-06 04:25:52 (9251) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-06 04:25:52 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 04:25:52 (9268) [INFO] 
* 2024-12-06 04:25:52 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 04:25:52 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-06 04:25:52 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-06 04:25:52 (9238) [INFO] 
* 2024-12-06 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-06 04:25:52 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-06 04:25:52 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-06 04:25:52 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-06 04:25:52 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-06 04:25:52 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-06 04:25:52 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-06 04:25:52 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-06 04:25:52 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-06 04:25:52 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-06 04:25:52 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-06 04:25:52 (9268) [INFO] 
* 2024-12-06 04:25:52 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-06 04:25:52 (9238) [INFO] 
* 2024-12-06 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-06 04:25:53 (9251) [INFO] Determining fastest mirrors
* 2024-12-06 04:25:57 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-06 04:25:57 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-06 04:25:57 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-06 04:25:57 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-06 04:25:57 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-06 04:25:57 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 04:25:57 (9251) [INFO] Trying other mirror.
* 2024-12-06 04:25:57 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-06 04:25:57 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-06 04:25:57 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-06 04:25:57 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-06 04:25:57 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-06 04:25:57 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-06 04:25:57 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-06 04:25:57 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-06 04:25:57 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-06 04:25:57 (9251) [INFO]         or
* 2024-12-06 04:25:57 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-06 04:25:57 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-06 04:25:57 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-06 04:25:57 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-06 04:25:57 (9251) [INFO]         compromise:
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-06 04:25:57 (9251) [INFO] 
* 2024-12-06 04:25:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-06 04:25:57 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 04:25:57 (9268) [INFO] 
* 2024-12-06 04:25:57 (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 04:25:57 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 04:25:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-06 04:25:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FigfhgsVKo/ea_profile.json
* 2024-12-06 04:26: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/FigfhgsVKo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-06 04:26:01 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-07 04:26:32 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-07 04:26:33 (10313) [INFO] Script is up to date.
* 2024-12-07 04:26:34 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-07 04:26:34 (9238) [INFO] 
* 2024-12-07 04:26:37 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-07 04:26:37 (9238) [INFO] 
* 2024-12-07 04:26:47 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-07 04:26:47 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-07 04:26:47 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-07 04:26:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-07 04:26:47 (9238) [INFO] 
* 2024-12-07 04:26:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-07 04:26:47 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-07 04:26:48 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-07 04:26:48 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-07 04:26:48 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-07 04:26:48 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-07 04:26:48 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-07 04:26:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 04:26:49 (9251) [INFO] Trying other mirror.
* 2024-12-07 04:26:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-07 04:26:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-07 04:26:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-07 04:26:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-07 04:26:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-07 04:26:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-07 04:26:49 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-07 04:26:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-07 04:26:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-07 04:26:49 (9251) [INFO]         or
* 2024-12-07 04:26:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-07 04:26:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-07 04:26:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-07 04:26:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-07 04:26:49 (9251) [INFO]         compromise:
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-07 04:26:49 (9251) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-07 04:26:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 04:26:49 (9268) [INFO] 
* 2024-12-07 04:26:49 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 04:26:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-07 04:26:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-07 04:26:49 (9238) [INFO] 
* 2024-12-07 04:26:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-07 04:26:49 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-07 04:26:49 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-07 04:26:49 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-07 04:26:49 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-07 04:26:49 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-07 04:26:49 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-07 04:26:49 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-07 04:26:49 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-07 04:26:49 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-07 04:26:49 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-07 04:26:49 (9268) [INFO] 
* 2024-12-07 04:26:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-07 04:26:49 (9238) [INFO] 
* 2024-12-07 04:26:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-07 04:26:50 (9251) [INFO] Determining fastest mirrors
* 2024-12-07 04:26:55 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-07 04:26:55 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-07 04:26:55 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-07 04:26:55 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-07 04:26:55 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-07 04:26:56 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 04:26:56 (9251) [INFO] Trying other mirror.
* 2024-12-07 04:26:56 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-07 04:26:56 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-07 04:26:56 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-07 04:26:56 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-07 04:26:56 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-07 04:26:56 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-07 04:26:56 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-07 04:26:56 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-07 04:26:56 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-07 04:26:56 (9251) [INFO]         or
* 2024-12-07 04:26:56 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-07 04:26:56 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-07 04:26:56 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-07 04:26:56 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-07 04:26:56 (9251) [INFO]         compromise:
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-07 04:26:56 (9251) [INFO] 
* 2024-12-07 04:26:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-07 04:26:56 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 04:26:56 (9268) [INFO] 
* 2024-12-07 04:26: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-07 04:26:56 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 04:26:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-07 04:26:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8nq_txP8V6/ea_profile.json
* 2024-12-07 04:26: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/8nq_txP8V6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-07 04:26:59 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-08 04:26:30 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-08 04:26:30 (10313) [INFO] Script is up to date.
* 2024-12-08 04:26:31 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-08 04:26:31 (9238) [INFO] 
* 2024-12-08 04:26:34 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-08 04:26:34 (9238) [INFO] 
* 2024-12-08 04:26:46 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-08 04:26:46 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-08 04:26:46 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-08 04:26:46 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-08 04:26:46 (9238) [INFO] 
* 2024-12-08 04:26:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-08 04:26:46 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-08 04:26:47 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-08 04:26:47 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-08 04:26:47 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-08 04:26:47 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-08 04:26:47 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-08 04:26:48 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 04:26:48 (9251) [INFO] Trying other mirror.
* 2024-12-08 04:26:48 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-08 04:26:48 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-08 04:26:48 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-08 04:26:48 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-08 04:26:48 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-08 04:26:48 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-08 04:26:48 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-08 04:26:48 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-08 04:26:48 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-08 04:26:48 (9251) [INFO]         or
* 2024-12-08 04:26:48 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-08 04:26:48 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-08 04:26:48 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-08 04:26:48 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-08 04:26:48 (9251) [INFO]         compromise:
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-08 04:26:48 (9251) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-08 04:26:48 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 04:26:48 (9268) [INFO] 
* 2024-12-08 04:26:48 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 04:26:48 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-08 04:26:48 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-08 04:26:48 (9238) [INFO] 
* 2024-12-08 04:26:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-08 04:26:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-08 04:26:48 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-08 04:26:48 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-08 04:26:48 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-08 04:26:48 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-08 04:26:48 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-08 04:26:48 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-08 04:26:48 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-08 04:26:49 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-08 04:26:49 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-08 04:26:49 (9268) [INFO] 
* 2024-12-08 04:26:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-08 04:26:49 (9238) [INFO] 
* 2024-12-08 04:26:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-08 04:26:49 (9251) [INFO] Determining fastest mirrors
* 2024-12-08 04:26:52 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-08 04:26:52 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-08 04:26:52 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-08 04:26:52 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-08 04:26:52 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-08 04:26:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 04:26:53 (9251) [INFO] Trying other mirror.
* 2024-12-08 04:26:53 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-08 04:26:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-08 04:26:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-08 04:26:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-08 04:26:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-08 04:26:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-08 04:26:53 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-08 04:26:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-08 04:26:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-08 04:26:53 (9251) [INFO]         or
* 2024-12-08 04:26:53 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-08 04:26:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-08 04:26:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-08 04:26:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-08 04:26:53 (9251) [INFO]         compromise:
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-08 04:26:53 (9251) [INFO] 
* 2024-12-08 04:26:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-08 04:26:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 04:26:53 (9268) [INFO] 
* 2024-12-08 04:26: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-08 04:26:53 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 04:26:53 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-08 04:26:54 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HXFkuSW19L/ea_profile.json
* 2024-12-08 04:26: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/HXFkuSW19L/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-08 04:26:56 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-09 04:25:35 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-09 04:25:35 (10313) [INFO] Script is up to date.
* 2024-12-09 04:25:36 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-09 04:25:36 (9238) [INFO] 
* 2024-12-09 04:25:38 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-09 04:25:38 (9238) [INFO] 
* 2024-12-09 04:25:45 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-09 04:25:45 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-09 04:25:45 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-09 04:25:45 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-09 04:25:45 (9238) [INFO] 
* 2024-12-09 04:25:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 04:25:45 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-09 04:25:48 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-09 04:25:48 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-09 04:25:48 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-09 04:25:48 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-09 04:25:48 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-09 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 04:25:49 (9251) [INFO] Trying other mirror.
* 2024-12-09 04:25:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-09 04:25:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-09 04:25:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-09 04:25:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-09 04:25:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-09 04:25:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-09 04:25:49 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-09 04:25:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-09 04:25:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-09 04:25:49 (9251) [INFO]         or
* 2024-12-09 04:25:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-09 04:25:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-09 04:25:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-09 04:25:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-09 04:25:49 (9251) [INFO]         compromise:
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-09 04:25:49 (9251) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-09 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 04:25:49 (9268) [INFO] 
* 2024-12-09 04:25:49 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 04:25:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-09 04:25:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-09 04:25:49 (9238) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 04:25:49 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-09 04:25:49 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-09 04:25:49 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-09 04:25:49 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-09 04:25:49 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-09 04:25:49 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-09 04:25:49 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-09 04:25:49 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-09 04:25:49 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-09 04:25:49 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-09 04:25:49 (9268) [INFO] 
* 2024-12-09 04:25:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-09 04:25:49 (9238) [INFO] 
* 2024-12-09 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 04:25:50 (9251) [INFO] Determining fastest mirrors
* 2024-12-09 04:25:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-09 04:25:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-09 04:25:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-09 04:25:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-09 04:25:53 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-09 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 04:25:54 (9251) [INFO] Trying other mirror.
* 2024-12-09 04:25:54 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-09 04:25:54 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-09 04:25:54 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-09 04:25:54 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-09 04:25:54 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-09 04:25:54 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-09 04:25:54 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-09 04:25:54 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-09 04:25:54 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-09 04:25:54 (9251) [INFO]         or
* 2024-12-09 04:25:54 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-09 04:25:54 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-09 04:25:54 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-09 04:25:54 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-09 04:25:54 (9251) [INFO]         compromise:
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-09 04:25:54 (9251) [INFO] 
* 2024-12-09 04:25:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-09 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 04:25:54 (9268) [INFO] 
* 2024-12-09 04:25:54 (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 04:25:54 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 04:25:54 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-09 04:25:55 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/J52jhvThoF/ea_profile.json
* 2024-12-09 04:25: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/J52jhvThoF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-09 04:25:57 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-10 04:25:46 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-10 04:25:46 (10313) [INFO] Script is up to date.
* 2024-12-10 04:25:47 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-10 04:25:47 (9238) [INFO] 
* 2024-12-10 04:25:50 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-10 04:25:50 (9238) [INFO] 
* 2024-12-10 04:25:57 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-10 04:25:57 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-10 04:25:57 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-10 04:25:57 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-10 04:25:57 (9238) [INFO] 
* 2024-12-10 04:25:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 04:25:57 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-10 04:25:59 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-10 04:25:59 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-10 04:25:59 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-10 04:25:59 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-10 04:25:59 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-10 04:25:59 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 04:25:59 (9251) [INFO] Trying other mirror.
* 2024-12-10 04:25:59 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-10 04:25:59 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-10 04:25:59 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-10 04:25:59 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-10 04:25:59 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-10 04:25:59 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-10 04:25:59 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-10 04:25:59 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-10 04:25:59 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-10 04:25:59 (9251) [INFO]         or
* 2024-12-10 04:25:59 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-10 04:25:59 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-10 04:25:59 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-10 04:25:59 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-10 04:25:59 (9251) [INFO]         compromise:
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-10 04:25:59 (9251) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-10 04:25:59 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 04:25:59 (9268) [INFO] 
* 2024-12-10 04:25:59 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 04:25:59 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-10 04:25:59 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-10 04:25:59 (9238) [INFO] 
* 2024-12-10 04:25:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 04:26:00 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-10 04:26:00 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-10 04:26:00 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-10 04:26:00 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-10 04:26:00 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-10 04:26:00 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-10 04:26:00 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-10 04:26:00 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-10 04:26:00 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-10 04:26:00 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-10 04:26:00 (9268) [INFO] 
* 2024-12-10 04:26:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-10 04:26:00 (9238) [INFO] 
* 2024-12-10 04:26:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 04:26:00 (9251) [INFO] Determining fastest mirrors
* 2024-12-10 04:26:04 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-10 04:26:04 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-10 04:26:04 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-10 04:26:04 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-10 04:26:04 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-10 04:26:04 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 04:26:04 (9251) [INFO] Trying other mirror.
* 2024-12-10 04:26:04 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-10 04:26:04 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-10 04:26:04 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-10 04:26:04 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-10 04:26:04 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-10 04:26:04 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-10 04:26:04 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-10 04:26:04 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-10 04:26:04 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-10 04:26:04 (9251) [INFO]         or
* 2024-12-10 04:26:04 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-10 04:26:04 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-10 04:26:04 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-10 04:26:04 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-10 04:26:04 (9251) [INFO]         compromise:
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-10 04:26:04 (9251) [INFO] 
* 2024-12-10 04:26:04 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-10 04:26:04 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 04:26:04 (9268) [INFO] 
* 2024-12-10 04:26: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-10 04:26:04 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 04:26:05 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-10 04:26:06 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/18JB41PrnS/ea_profile.json
* 2024-12-10 04:26: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/18JB41PrnS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-10 04:26:08 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-11 04:26:24 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-11 04:26:24 (10313) [INFO] Script is up to date.
* 2024-12-11 04:26:26 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-11 04:26:26 (9238) [INFO] 
* 2024-12-11 04:26:29 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-11 04:26:29 (9238) [INFO] 
* 2024-12-11 04:26:37 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-11 04:26:37 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-11 04:26:37 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-11 04:26:37 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-11 04:26:37 (9238) [INFO] 
* 2024-12-11 04:26:37 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 04:26:37 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-11 04:26:39 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-11 04:26:39 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-11 04:26:39 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-11 04:26:39 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-11 04:26:39 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-11 04:26:39 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 04:26:39 (9251) [INFO] Trying other mirror.
* 2024-12-11 04:26:39 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-11 04:26:39 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-11 04:26:39 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-11 04:26:39 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-11 04:26:39 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-11 04:26:39 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-11 04:26:39 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-11 04:26:39 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-11 04:26:39 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-11 04:26:39 (9251) [INFO]         or
* 2024-12-11 04:26:39 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-11 04:26:39 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-11 04:26:39 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-11 04:26:39 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-11 04:26:39 (9251) [INFO]         compromise:
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-11 04:26:39 (9251) [INFO] 
* 2024-12-11 04:26:39 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-11 04:26:39 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 04:26:39 (9268) [INFO] 
* 2024-12-11 04:26:39 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 04:26:39 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-11 04:26:39 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-11 04:26:39 (9238) [INFO] 
* 2024-12-11 04:26:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 04:26:40 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-11 04:26:40 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-11 04:26:40 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-11 04:26:40 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-11 04:26:40 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-11 04:26:40 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-11 04:26:40 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-11 04:26:40 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-11 04:26:40 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-11 04:26:40 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-11 04:26:40 (9268) [INFO] 
* 2024-12-11 04:26:40 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-11 04:26:40 (9238) [INFO] 
* 2024-12-11 04:26:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 04:26:40 (9251) [INFO] Determining fastest mirrors
* 2024-12-11 04:26:44 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-11 04:26:44 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-11 04:26:44 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-11 04:26:44 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-11 04:26:44 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-11 04:26:44 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 04:26:44 (9251) [INFO] Trying other mirror.
* 2024-12-11 04:26:44 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-11 04:26:44 (9251) [INFO] 
* 2024-12-11 04:26:44 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-11 04:26:44 (9251) [INFO] 
* 2024-12-11 04:26:44 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-11 04:26:44 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-11 04:26:45 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-11 04:26:45 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-11 04:26:45 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-11 04:26:45 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-11 04:26:45 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-11 04:26:45 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-11 04:26:45 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-11 04:26:45 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-11 04:26:45 (9251) [INFO]         or
* 2024-12-11 04:26:45 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-11 04:26:45 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-11 04:26:45 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-11 04:26:45 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-11 04:26:45 (9251) [INFO]         compromise:
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-11 04:26:45 (9251) [INFO] 
* 2024-12-11 04:26:45 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-11 04:26:45 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 04:26:45 (9268) [INFO] 
* 2024-12-11 04:26: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-11 04:26:45 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 04:26:45 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-11 04:26:46 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cbCjALQbMc/ea_profile.json
* 2024-12-11 04:26: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/cbCjALQbMc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-11 04:26:48 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-12 04:25:34 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-12 04:25:35 (10313) [INFO] Script is up to date.
* 2024-12-12 04:25:36 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-12 04:25:36 (9238) [INFO] 
* 2024-12-12 04:25:38 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-12 04:25:38 (9238) [INFO] 
* 2024-12-12 04:25:45 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-12 04:25:45 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-12 04:25:45 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-12 04:25:45 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-12 04:25:45 (9238) [INFO] 
* 2024-12-12 04:25:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 04:25:45 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-12 04:25:46 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-12 04:25:46 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-12 04:25:46 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-12 04:25:46 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-12 04:25:46 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-12 04:25:47 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 04:25:47 (9251) [INFO] Trying other mirror.
* 2024-12-12 04:25:47 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-12 04:25:47 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-12 04:25:47 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-12 04:25:47 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-12 04:25:47 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-12 04:25:47 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-12 04:25:47 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-12 04:25:47 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-12 04:25:47 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-12 04:25:47 (9251) [INFO]         or
* 2024-12-12 04:25:47 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-12 04:25:47 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-12 04:25:47 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-12 04:25:47 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-12 04:25:47 (9251) [INFO]         compromise:
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-12 04:25:47 (9251) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-12 04:25:47 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 04:25:47 (9268) [INFO] 
* 2024-12-12 04:25:47 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 04:25:47 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-12 04:25:47 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-12 04:25:47 (9238) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 04:25:47 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-12 04:25:47 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-12 04:25:47 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-12 04:25:47 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-12 04:25:47 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-12 04:25:47 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-12 04:25:47 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-12 04:25:47 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-12 04:25:47 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-12 04:25:47 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-12 04:25:47 (9268) [INFO] 
* 2024-12-12 04:25:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-12 04:25:47 (9238) [INFO] 
* 2024-12-12 04:25:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 04:25:47 (9251) [INFO] Determining fastest mirrors
* 2024-12-12 04:25:50 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-12 04:25:50 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-12 04:25:50 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-12 04:25:50 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-12 04:25:50 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-12 04:25:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 04:25:51 (9251) [INFO] Trying other mirror.
* 2024-12-12 04:25:51 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-12 04:25:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-12 04:25:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-12 04:25:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-12 04:25:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-12 04:25:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-12 04:25:51 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-12 04:25:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-12 04:25:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-12 04:25:51 (9251) [INFO]         or
* 2024-12-12 04:25:51 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-12 04:25:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-12 04:25:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-12 04:25:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-12 04:25:51 (9251) [INFO]         compromise:
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-12 04:25:51 (9251) [INFO] 
* 2024-12-12 04:25:51 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-12 04:25:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 04:25:51 (9268) [INFO] 
* 2024-12-12 04:25: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-12 04:25:51 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 04:25:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-12 04:25:52 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5Ds6Nw7s3H/ea_profile.json
* 2024-12-12 04:25: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/5Ds6Nw7s3H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-12 04:25:54 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-13 04:25:35 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-13 04:25:35 (10313) [INFO] Script is up to date.
* 2024-12-13 04:25:36 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-13 04:25:36 (9238) [INFO] 
* 2024-12-13 04:25:39 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-13 04:25:39 (9238) [INFO] 
* 2024-12-13 04:25:47 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-13 04:25:47 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-13 04:25:47 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-13 04:25:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-13 04:25:47 (9238) [INFO] 
* 2024-12-13 04:25:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 04:25:47 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-13 04:25:49 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-13 04:25:49 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-13 04:25:49 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-13 04:25:49 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-13 04:25:49 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-13 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 04:25:49 (9251) [INFO] Trying other mirror.
* 2024-12-13 04:25:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-13 04:25:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 04:25:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 04:25:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-13 04:25:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-13 04:25:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-13 04:25:49 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 04:25:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-13 04:25:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-13 04:25:49 (9251) [INFO]         or
* 2024-12-13 04:25:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 04:25:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 04:25:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 04:25:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 04:25:49 (9251) [INFO]         compromise:
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-13 04:25:49 (9251) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-13 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 04:25:49 (9268) [INFO] 
* 2024-12-13 04:25:49 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 04:25:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-13 04:25:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-13 04:25:49 (9238) [INFO] 
* 2024-12-13 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 04:25:50 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-13 04:25:50 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-13 04:25:50 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-13 04:25:50 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-13 04:25:50 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-13 04:25:50 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-13 04:25:50 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-13 04:25:50 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-13 04:25:50 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-13 04:25:50 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-13 04:25:50 (9268) [INFO] 
* 2024-12-13 04:25:50 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-13 04:25:50 (9238) [INFO] 
* 2024-12-13 04:25:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 04:25:50 (9251) [INFO] Determining fastest mirrors
* 2024-12-13 04:25:54 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-13 04:25:54 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-13 04:25:54 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-13 04:25:54 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-13 04:25:54 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-13 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 04:25:54 (9251) [INFO] Trying other mirror.
* 2024-12-13 04:25:54 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-13 04:25:54 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 04:25:54 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 04:25:54 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-13 04:25:54 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-13 04:25:54 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-13 04:25:54 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 04:25:54 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-13 04:25:54 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-13 04:25:54 (9251) [INFO]         or
* 2024-12-13 04:25:54 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 04:25:54 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 04:25:54 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 04:25:54 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 04:25:54 (9251) [INFO]         compromise:
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-13 04:25:54 (9251) [INFO] 
* 2024-12-13 04:25:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-13 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 04:25:54 (9268) [INFO] 
* 2024-12-13 04:25: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-13 04:25:55 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 04:25:55 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-13 04:25:56 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FieFj6FVy1/ea_profile.json
* 2024-12-13 04:25: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/FieFj6FVy1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-13 04:25:58 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-14 04:26:26 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-14 04:26:26 (10313) [INFO] Script is up to date.
* 2024-12-14 04:26:27 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-14 04:26:27 (9238) [INFO] 
* 2024-12-14 04:26:31 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-14 04:26:31 (9238) [INFO] 
* 2024-12-14 04:26:38 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-14 04:26:38 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-14 04:26:38 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-14 04:26:38 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-14 04:26:38 (9238) [INFO] 
* 2024-12-14 04:26:39 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 04:26:39 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-14 04:26:40 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-14 04:26:40 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-14 04:26:40 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-14 04:26:40 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-14 04:26:40 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-14 04:26:41 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 04:26:41 (9251) [INFO] Trying other mirror.
* 2024-12-14 04:26:41 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-14 04:26:41 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-14 04:26:41 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-14 04:26:41 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-14 04:26:41 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-14 04:26:41 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-14 04:26:41 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-14 04:26:41 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-14 04:26:41 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-14 04:26:41 (9251) [INFO]         or
* 2024-12-14 04:26:41 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-14 04:26:41 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-14 04:26:41 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-14 04:26:41 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-14 04:26:41 (9251) [INFO]         compromise:
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-14 04:26:41 (9251) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-14 04:26:41 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 04:26:41 (9268) [INFO] 
* 2024-12-14 04:26:41 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 04:26:41 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-14 04:26:41 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-14 04:26:41 (9238) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 04:26:41 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-14 04:26:41 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-14 04:26:41 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-14 04:26:41 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-14 04:26:41 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-14 04:26:41 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-14 04:26:41 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-14 04:26:41 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-14 04:26:41 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-14 04:26:41 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-14 04:26:41 (9268) [INFO] 
* 2024-12-14 04:26:41 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-14 04:26:41 (9238) [INFO] 
* 2024-12-14 04:26:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 04:26:41 (9251) [INFO] Determining fastest mirrors
* 2024-12-14 04:26:45 (9251) [INFO]  * EA4: 63.247.64.58
* 2024-12-14 04:26:45 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-12-14 04:26:45 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-12-14 04:26:45 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-14 04:26:45 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-14 04:26:45 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 04:26:45 (9251) [INFO] Trying other mirror.
* 2024-12-14 04:26:45 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-14 04:26:45 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-14 04:26:45 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-14 04:26:45 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-14 04:26:45 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-14 04:26:45 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-14 04:26:45 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-14 04:26:45 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-14 04:26:45 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-14 04:26:45 (9251) [INFO]         or
* 2024-12-14 04:26:45 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-14 04:26:45 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-14 04:26:45 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-14 04:26:45 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-14 04:26:45 (9251) [INFO]         compromise:
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-14 04:26:45 (9251) [INFO] 
* 2024-12-14 04:26:45 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-14 04:26:45 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 04:26:45 (9268) [INFO] 
* 2024-12-14 04:26: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-14 04:26:45 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 04:26:46 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-14 04:26:47 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RXc8vt6Onu/ea_profile.json
* 2024-12-14 04:26: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/RXc8vt6Onu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-14 04:26:48 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-15 04:26:26 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-15 04:26:26 (10313) [INFO] Script is up to date.
* 2024-12-15 04:26:28 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-15 04:26:28 (9238) [INFO] 
* 2024-12-15 04:26:30 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-15 04:26:30 (9238) [INFO] 
* 2024-12-15 04:26:38 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-15 04:26:38 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-15 04:26:38 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-15 04:26:38 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-15 04:26:38 (9238) [INFO] 
* 2024-12-15 04:26:38 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 04:26:38 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-15 04:26:39 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-15 04:26:39 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-15 04:26:39 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-15 04:26:39 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-15 04:26:39 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-15 04:26:40 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 04:26:40 (9251) [INFO] Trying other mirror.
* 2024-12-15 04:26:40 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-15 04:26:40 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-15 04:26:40 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-15 04:26:40 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-15 04:26:40 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-15 04:26:40 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-15 04:26:40 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-15 04:26:40 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-15 04:26:40 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-15 04:26:40 (9251) [INFO]         or
* 2024-12-15 04:26:40 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-15 04:26:40 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-15 04:26:40 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-15 04:26:40 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-15 04:26:40 (9251) [INFO]         compromise:
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-15 04:26:40 (9251) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-15 04:26:40 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 04:26:40 (9268) [INFO] 
* 2024-12-15 04:26:40 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 04:26:40 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-15 04:26:40 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-15 04:26:40 (9238) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 04:26:40 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-15 04:26:40 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-15 04:26:40 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-15 04:26:40 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-15 04:26:40 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-15 04:26:40 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-15 04:26:40 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-15 04:26:40 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-15 04:26:40 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-15 04:26:40 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-15 04:26:40 (9268) [INFO] 
* 2024-12-15 04:26:40 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-15 04:26:40 (9238) [INFO] 
* 2024-12-15 04:26:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 04:26:40 (9251) [INFO] Determining fastest mirrors
* 2024-12-15 04:26:44 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-15 04:26:44 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-15 04:26:44 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-15 04:26:44 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-15 04:26:44 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-15 04:26:44 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 04:26:44 (9251) [INFO] Trying other mirror.
* 2024-12-15 04:26:44 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-15 04:26:44 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-15 04:26:44 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-15 04:26:44 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-15 04:26:44 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-15 04:26:44 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-15 04:26:44 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-15 04:26:44 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-15 04:26:44 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-15 04:26:44 (9251) [INFO]         or
* 2024-12-15 04:26:44 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-15 04:26:44 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-15 04:26:44 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-15 04:26:44 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-15 04:26:44 (9251) [INFO]         compromise:
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-15 04:26:44 (9251) [INFO] 
* 2024-12-15 04:26:44 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-15 04:26:44 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 04:26:44 (9268) [INFO] 
* 2024-12-15 04:26: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/
* 2024-12-15 04:26:44 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 04:26:44 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-15 04:26:45 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hGFVOcPOQ4/ea_profile.json
* 2024-12-15 04:26: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/hGFVOcPOQ4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-15 04:26:47 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-16 04:25:35 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-16 04:25:35 (10313) [INFO] Script is up to date.
* 2024-12-16 04:25:37 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-16 04:25:37 (9238) [INFO] 
* 2024-12-16 04:25:39 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-16 04:25:39 (9238) [INFO] 
* 2024-12-16 04:25:52 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-16 04:25:52 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-16 04:25:52 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-16 04:25:52 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-16 04:25:52 (9238) [INFO] 
* 2024-12-16 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 04:25:52 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-16 04:25:54 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-16 04:25:54 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-16 04:25:54 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-16 04:25:54 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-16 04:25:54 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-16 04:25:55 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 04:25:55 (9251) [INFO] Trying other mirror.
* 2024-12-16 04:25:55 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-16 04:25:55 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-16 04:25:55 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-16 04:25:55 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-16 04:25:55 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-16 04:25:55 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-16 04:25:55 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-16 04:25:55 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-16 04:25:55 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-16 04:25:55 (9251) [INFO]         or
* 2024-12-16 04:25:55 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-16 04:25:55 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-16 04:25:55 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-16 04:25:55 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-16 04:25:55 (9251) [INFO]         compromise:
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-16 04:25:55 (9251) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-16 04:25:55 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 04:25:55 (9268) [INFO] 
* 2024-12-16 04:25:55 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 04:25:55 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-16 04:25:55 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-16 04:25:55 (9238) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 04:25:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-16 04:25:55 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-16 04:25:55 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-16 04:25:55 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-16 04:25:55 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-16 04:25:55 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-16 04:25:55 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-16 04:25:55 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-16 04:25:55 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-16 04:25:55 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-16 04:25:55 (9268) [INFO] 
* 2024-12-16 04:25:55 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-16 04:25:55 (9238) [INFO] 
* 2024-12-16 04:25:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 04:25:56 (9251) [INFO] Determining fastest mirrors
* 2024-12-16 04:25:59 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-16 04:25:59 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-16 04:25:59 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-16 04:25:59 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-16 04:25:59 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-16 04:26:00 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 04:26:00 (9251) [INFO] Trying other mirror.
* 2024-12-16 04:26:00 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-16 04:26:00 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-16 04:26:00 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-16 04:26:00 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-16 04:26:00 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-16 04:26:00 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-16 04:26:00 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-16 04:26:00 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-16 04:26:00 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-16 04:26:00 (9251) [INFO]         or
* 2024-12-16 04:26:00 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-16 04:26:00 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-16 04:26:00 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-16 04:26:00 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-16 04:26:00 (9251) [INFO]         compromise:
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-16 04:26:00 (9251) [INFO] 
* 2024-12-16 04:26:00 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-16 04:26:00 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 04:26:00 (9268) [INFO] 
* 2024-12-16 04:26:00 (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 04:26:00 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 04:26:00 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-16 04:26:01 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UWhetzLKCh/ea_profile.json
* 2024-12-16 04:26:04 (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/UWhetzLKCh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-16 04:26:04 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-17 04:25:43 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-17 04:25:43 (10313) [INFO] Script is up to date.
* 2024-12-17 04:25:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-17 04:25:45 (9238) [INFO] 
* 2024-12-17 04:25:48 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-17 04:25:48 (9238) [INFO] 
* 2024-12-17 04:25:56 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-17 04:25:56 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-17 04:25:56 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-17 04:25:56 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-17 04:25:56 (9238) [INFO] 
* 2024-12-17 04:25:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 04:25:56 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-17 04:25:57 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-17 04:25:57 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-17 04:25:57 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-17 04:25:57 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-17 04:25:57 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-17 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 04:25:58 (9251) [INFO] Trying other mirror.
* 2024-12-17 04:25:58 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-17 04:25:58 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 04:25:58 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 04:25:58 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-17 04:25:58 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-17 04:25:58 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-17 04:25:58 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 04:25:58 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-17 04:25:58 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-17 04:25:58 (9251) [INFO]         or
* 2024-12-17 04:25:58 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 04:25:58 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 04:25:58 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 04:25:58 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 04:25:58 (9251) [INFO]         compromise:
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-17 04:25:58 (9251) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-17 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 04:25:58 (9268) [INFO] 
* 2024-12-17 04:25:58 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 04:25:58 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-17 04:25:58 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-17 04:25:58 (9238) [INFO] 
* 2024-12-17 04:25:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 04:25:58 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-17 04:25:58 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-17 04:25:58 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-17 04:25:58 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-17 04:25:58 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-17 04:25:58 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-17 04:25:58 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-17 04:25:58 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-17 04:25:58 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-17 04:25:58 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-17 04:25:58 (9268) [INFO] 
* 2024-12-17 04:25:58 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-17 04:25:58 (9238) [INFO] 
* 2024-12-17 04:25:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 04:25:59 (9251) [INFO] Determining fastest mirrors
* 2024-12-17 04:26:02 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-17 04:26:03 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-17 04:26:03 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-17 04:26:03 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-17 04:26:03 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-17 04:26:03 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 04:26:03 (9251) [INFO] Trying other mirror.
* 2024-12-17 04:26:03 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-17 04:26:03 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 04:26:03 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 04:26:03 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-17 04:26:03 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-17 04:26:03 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-17 04:26:03 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 04:26:03 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-17 04:26:03 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-17 04:26:03 (9251) [INFO]         or
* 2024-12-17 04:26:03 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 04:26:03 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 04:26:03 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 04:26:03 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 04:26:03 (9251) [INFO]         compromise:
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-17 04:26:03 (9251) [INFO] 
* 2024-12-17 04:26:03 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-17 04:26:03 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 04:26:03 (9268) [INFO] 
* 2024-12-17 04:26:03 (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 04:26:03 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 04:26:03 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-17 04:26:04 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EirVRvsY5g/ea_profile.json
* 2024-12-17 04:26:07 (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/EirVRvsY5g/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-17 04:26:07 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-18 04:25:39 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-18 04:25:39 (10313) [INFO] Script is up to date.
* 2024-12-18 04:25:40 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-18 04:25:40 (9238) [INFO] 
* 2024-12-18 04:25:42 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-18 04:25:42 (9238) [INFO] 
* 2024-12-18 04:25:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-18 04:25:49 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-18 04:25:49 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-18 04:25:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-18 04:25:49 (9238) [INFO] 
* 2024-12-18 04:25:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 04:25:50 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-18 04:25:51 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-18 04:25:51 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-18 04:25:51 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-18 04:25:51 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-18 04:25:51 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-18 04:25:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 04:25:51 (9251) [INFO] Trying other mirror.
* 2024-12-18 04:25:51 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-18 04:25:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-18 04:25:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-18 04:25:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-18 04:25:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-18 04:25:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-18 04:25:51 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-18 04:25:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-18 04:25:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-18 04:25:51 (9251) [INFO]         or
* 2024-12-18 04:25:51 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-18 04:25:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-18 04:25:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-18 04:25:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-18 04:25:51 (9251) [INFO]         compromise:
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-18 04:25:51 (9251) [INFO] 
* 2024-12-18 04:25:51 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-18 04:25:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 04:25:51 (9268) [INFO] 
* 2024-12-18 04:25:51 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 04:25:51 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-18 04:25:51 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-18 04:25:51 (9238) [INFO] 
* 2024-12-18 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 04:25:52 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-18 04:25:52 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-18 04:25:52 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-18 04:25:52 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-18 04:25:52 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-18 04:25:52 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-18 04:25:52 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-18 04:25:52 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-18 04:25:52 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-18 04:25:52 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-18 04:25:52 (9268) [INFO] 
* 2024-12-18 04:25:52 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-18 04:25:52 (9238) [INFO] 
* 2024-12-18 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 04:25:52 (9251) [INFO] Determining fastest mirrors
* 2024-12-18 04:25:56 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-18 04:25:56 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-18 04:25:56 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-18 04:25:56 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-18 04:25:56 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-18 04:25:57 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 04:25:57 (9251) [INFO] Trying other mirror.
* 2024-12-18 04:25:57 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-18 04:25:57 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-18 04:25:57 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-18 04:25:57 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-18 04:25:57 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-18 04:25:57 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-18 04:25:57 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-18 04:25:57 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-18 04:25:57 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-18 04:25:57 (9251) [INFO]         or
* 2024-12-18 04:25:57 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-18 04:25:57 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-18 04:25:57 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-18 04:25:57 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-18 04:25:57 (9251) [INFO]         compromise:
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-18 04:25:57 (9251) [INFO] 
* 2024-12-18 04:25:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-18 04:25:57 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 04:25:57 (9268) [INFO] 
* 2024-12-18 04:25:57 (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 04:25:57 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 04:25:57 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-18 04:25:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HQo5beVXLV/ea_profile.json
* 2024-12-18 04:26: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/HQo5beVXLV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-18 04:26:00 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-19 04:25:37 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-19 04:25:38 (10313) [INFO] Script is up to date.
* 2024-12-19 04:25:39 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-19 04:25:39 (9238) [INFO] 
* 2024-12-19 04:25:41 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-19 04:25:41 (9238) [INFO] 
* 2024-12-19 04:25:47 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-19 04:25:47 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-19 04:25:47 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-19 04:25:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-19 04:25:47 (9238) [INFO] 
* 2024-12-19 04:25:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 04:25:47 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-19 04:25:48 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-19 04:25:48 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-19 04:25:48 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-19 04:25:48 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-19 04:25:48 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-19 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 04:25:49 (9251) [INFO] Trying other mirror.
* 2024-12-19 04:25:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-19 04:25:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-19 04:25:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-19 04:25:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-19 04:25:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-19 04:25:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-19 04:25:49 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-19 04:25:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-19 04:25:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-19 04:25:49 (9251) [INFO]         or
* 2024-12-19 04:25:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-19 04:25:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-19 04:25:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-19 04:25:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-19 04:25:49 (9251) [INFO]         compromise:
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-19 04:25:49 (9251) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-19 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 04:25:49 (9268) [INFO] 
* 2024-12-19 04:25:49 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 04:25:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-19 04:25:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-19 04:25:49 (9238) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 04:25:49 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-19 04:25:49 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-19 04:25:49 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-19 04:25:49 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-19 04:25:49 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-19 04:25:49 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-19 04:25:49 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-19 04:25:49 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-19 04:25:49 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-19 04:25:49 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-19 04:25:49 (9268) [INFO] 
* 2024-12-19 04:25:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-19 04:25:49 (9238) [INFO] 
* 2024-12-19 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 04:25:50 (9251) [INFO] Determining fastest mirrors
* 2024-12-19 04:25:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-19 04:25:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-19 04:25:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-19 04:25:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-19 04:25:53 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-19 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 04:25:53 (9251) [INFO] Trying other mirror.
* 2024-12-19 04:25:53 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-19 04:25:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-19 04:25:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-19 04:25:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-19 04:25:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-19 04:25:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-19 04:25:53 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-19 04:25:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-19 04:25:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-19 04:25:53 (9251) [INFO]         or
* 2024-12-19 04:25:53 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-19 04:25:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-19 04:25:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-19 04:25:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-19 04:25:53 (9251) [INFO]         compromise:
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-19 04:25:53 (9251) [INFO] 
* 2024-12-19 04:25:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-19 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 04:25:53 (9268) [INFO] 
* 2024-12-19 04:25: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-19 04:25:53 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 04:25:54 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-19 04:25:54 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gc4NCAoYay/ea_profile.json
* 2024-12-19 04:25: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/gc4NCAoYay/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-19 04:25:56 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-20 04:25:40 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-20 04:25:40 (10313) [INFO] Script is up to date.
* 2024-12-20 04:25:42 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-20 04:25:42 (9238) [INFO] 
* 2024-12-20 04:25:45 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-20 04:25:45 (9238) [INFO] 
* 2024-12-20 04:25:53 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-20 04:25:53 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-20 04:25:53 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-20 04:25:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-20 04:25:53 (9238) [INFO] 
* 2024-12-20 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 04:25:53 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-20 04:25:55 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-20 04:25:55 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-20 04:25:55 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-20 04:25:55 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-20 04:25:55 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-20 04:25:55 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 04:25:55 (9251) [INFO] Trying other mirror.
* 2024-12-20 04:25:55 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-20 04:25:55 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 04:25:55 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 04:25:55 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-20 04:25:55 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-20 04:25:55 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-20 04:25:55 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 04:25:55 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-20 04:25:55 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-20 04:25:55 (9251) [INFO]         or
* 2024-12-20 04:25:55 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 04:25:55 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 04:25:55 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 04:25:55 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 04:25:55 (9251) [INFO]         compromise:
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-20 04:25:55 (9251) [INFO] 
* 2024-12-20 04:25:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-20 04:25:55 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 04:25:56 (9268) [INFO] 
* 2024-12-20 04:25:56 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 04:25:56 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-20 04:25:56 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-20 04:25:56 (9238) [INFO] 
* 2024-12-20 04:25:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 04:25:56 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-20 04:25:56 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-20 04:25:56 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-20 04:25:56 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-20 04:25:56 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-20 04:25:56 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-20 04:25:56 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-20 04:25:56 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-20 04:25:56 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-20 04:25:56 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-20 04:25:57 (9268) [INFO] 
* 2024-12-20 04:25:57 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-20 04:25:57 (9238) [INFO] 
* 2024-12-20 04:25:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 04:25:57 (9251) [INFO] Determining fastest mirrors
* 2024-12-20 04:26:01 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-20 04:26:01 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-20 04:26:01 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-20 04:26:01 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-20 04:26:01 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-20 04:26:02 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 04:26:02 (9251) [INFO] Trying other mirror.
* 2024-12-20 04:26:02 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-20 04:26:02 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 04:26:02 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 04:26:02 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-20 04:26:02 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-20 04:26:02 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-20 04:26:02 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 04:26:02 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-20 04:26:02 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-20 04:26:02 (9251) [INFO]         or
* 2024-12-20 04:26:02 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 04:26:02 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 04:26:02 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 04:26:02 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 04:26:02 (9251) [INFO]         compromise:
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-20 04:26:02 (9251) [INFO] 
* 2024-12-20 04:26:02 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-20 04:26:02 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 04:26:02 (9268) [INFO] 
* 2024-12-20 04:26: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-20 04:26:02 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 04:26:02 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-20 04:26:03 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0yq92RIUsb/ea_profile.json
* 2024-12-20 04:26:05 (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/0yq92RIUsb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-20 04:26:05 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-21 04:26:29 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-21 04:26:29 (10313) [INFO] Script is up to date.
* 2024-12-21 04:26:30 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-21 04:26:30 (9238) [INFO] 
* 2024-12-21 04:26:34 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-21 04:26:34 (9238) [INFO] 
* 2024-12-21 04:26:42 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-21 04:26:42 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-21 04:26:42 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-21 04:26:42 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-21 04:26:42 (9238) [INFO] 
* 2024-12-21 04:26:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 04:26:42 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-21 04:26:44 (9251) [INFO]  * EA4: 63.247.64.58
* 2024-12-21 04:26:44 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-12-21 04:26:44 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-12-21 04:26:44 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-21 04:26:44 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-21 04:26:44 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 04:26:44 (9251) [INFO] Trying other mirror.
* 2024-12-21 04:26:44 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-21 04:26:44 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-21 04:26:44 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-21 04:26:44 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-21 04:26:44 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-21 04:26:44 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-21 04:26:44 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-21 04:26:44 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-21 04:26:44 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-21 04:26:44 (9251) [INFO]         or
* 2024-12-21 04:26:44 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-21 04:26:44 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-21 04:26:44 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-21 04:26:44 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-21 04:26:44 (9251) [INFO]         compromise:
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-21 04:26:44 (9251) [INFO] 
* 2024-12-21 04:26:44 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-21 04:26:44 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 04:26:44 (9268) [INFO] 
* 2024-12-21 04:26:44 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 04:26:44 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-21 04:26:44 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-21 04:26:44 (9238) [INFO] 
* 2024-12-21 04:26:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 04:26:45 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-21 04:26:45 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-21 04:26:45 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-21 04:26:45 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-21 04:26:45 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-21 04:26:45 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-21 04:26:45 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-21 04:26:45 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-21 04:26:45 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-21 04:26:45 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-21 04:26:45 (9268) [INFO] 
* 2024-12-21 04:26:45 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-21 04:26:45 (9238) [INFO] 
* 2024-12-21 04:26:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 04:26:45 (9251) [INFO] Determining fastest mirrors
* 2024-12-21 04:26:49 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-21 04:26:49 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-21 04:26:49 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-21 04:26:49 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-21 04:26:49 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-21 04:26:50 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 04:26:50 (9251) [INFO] Trying other mirror.
* 2024-12-21 04:26:50 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-21 04:26:50 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-21 04:26:50 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-21 04:26:50 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-21 04:26:50 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-21 04:26:50 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-21 04:26:50 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-21 04:26:50 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-21 04:26:50 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-21 04:26:50 (9251) [INFO]         or
* 2024-12-21 04:26:50 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-21 04:26:50 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-21 04:26:50 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-21 04:26:50 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-21 04:26:50 (9251) [INFO]         compromise:
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-21 04:26:50 (9251) [INFO] 
* 2024-12-21 04:26:50 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-21 04:26:50 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 04:26:50 (9268) [INFO] 
* 2024-12-21 04:26: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/
* 2024-12-21 04:26:50 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 04:26:50 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-21 04:26:51 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ycnp4c2kPM/ea_profile.json
* 2024-12-21 04:26: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/Ycnp4c2kPM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-21 04:26:53 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-22 04:26:32 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-22 04:26:32 (10313) [INFO] Script is up to date.
* 2024-12-22 04:26:33 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-22 04:26:33 (9238) [INFO] 
* 2024-12-22 04:26:37 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-22 04:26:37 (9238) [INFO] 
* 2024-12-22 04:26:44 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-22 04:26:44 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-22 04:26:44 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-22 04:26:44 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-22 04:26:44 (9238) [INFO] 
* 2024-12-22 04:26:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 04:26:45 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-22 04:26:46 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-22 04:26:46 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-22 04:26:46 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-22 04:26:46 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-22 04:26:46 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-22 04:26:46 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 04:26:46 (9251) [INFO] Trying other mirror.
* 2024-12-22 04:26:46 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-22 04:26:46 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-22 04:26:46 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-22 04:26:46 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-22 04:26:46 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-22 04:26:46 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-22 04:26:46 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-22 04:26:46 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-22 04:26:46 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-22 04:26:46 (9251) [INFO]         or
* 2024-12-22 04:26:46 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-22 04:26:46 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-22 04:26:46 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-22 04:26:46 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-22 04:26:46 (9251) [INFO]         compromise:
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-22 04:26:46 (9251) [INFO] 
* 2024-12-22 04:26:46 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-22 04:26:46 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 04:26:46 (9268) [INFO] 
* 2024-12-22 04:26:46 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 04:26:46 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-22 04:26:46 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-22 04:26:46 (9238) [INFO] 
* 2024-12-22 04:26:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 04:26:47 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-22 04:26:47 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-22 04:26:47 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-22 04:26:47 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-22 04:26:47 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-22 04:26:47 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-22 04:26:47 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-22 04:26:47 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-22 04:26:47 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-22 04:26:47 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-22 04:26:47 (9268) [INFO] 
* 2024-12-22 04:26:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-22 04:26:47 (9238) [INFO] 
* 2024-12-22 04:26:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 04:26:47 (9251) [INFO] Determining fastest mirrors
* 2024-12-22 04:26:51 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-22 04:26:51 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-22 04:26:51 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-22 04:26:51 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-22 04:26:51 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-22 04:26:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 04:26:51 (9251) [INFO] Trying other mirror.
* 2024-12-22 04:26:51 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-22 04:26:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-22 04:26:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-22 04:26:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-22 04:26:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-22 04:26:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-22 04:26:51 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-22 04:26:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-22 04:26:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-22 04:26:51 (9251) [INFO]         or
* 2024-12-22 04:26:51 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-22 04:26:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-22 04:26:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-22 04:26:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-22 04:26:51 (9251) [INFO]         compromise:
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-22 04:26:51 (9251) [INFO] 
* 2024-12-22 04:26:51 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-22 04:26:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 04:26:51 (9268) [INFO] 
* 2024-12-22 04:26: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-22 04:26:51 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 04:26:52 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-22 04:26:53 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FiEAXmnRg7/ea_profile.json
* 2024-12-22 04:26: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/FiEAXmnRg7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-22 04:26:55 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-23 04:25:40 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-23 04:25:40 (10313) [INFO] Script is up to date.
* 2024-12-23 04:25:41 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-23 04:25:41 (9238) [INFO] 
* 2024-12-23 04:25:44 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-23 04:25:44 (9238) [INFO] 
* 2024-12-23 04:25:51 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-23 04:25:51 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-23 04:25:51 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-23 04:25:51 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-23 04:25:51 (9238) [INFO] 
* 2024-12-23 04:25:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 04:25:51 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-23 04:25:57 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-23 04:25:57 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-23 04:25:57 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-23 04:25:57 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-23 04:25:57 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-23 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 04:25:58 (9251) [INFO] Trying other mirror.
* 2024-12-23 04:25:58 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-23 04:25:58 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-23 04:25:58 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-23 04:25:58 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-23 04:25:58 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-23 04:25:58 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-23 04:25:58 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-23 04:25:58 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-23 04:25:58 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-23 04:25:58 (9251) [INFO]         or
* 2024-12-23 04:25:58 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-23 04:25:58 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-23 04:25:58 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-23 04:25:58 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-23 04:25:58 (9251) [INFO]         compromise:
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-23 04:25:58 (9251) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-23 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 04:25:58 (9268) [INFO] 
* 2024-12-23 04:25:58 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 04:25:58 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-23 04:25:58 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-23 04:25:58 (9238) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 04:25:58 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-23 04:25:58 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-23 04:25:58 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-23 04:25:58 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-23 04:25:58 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-23 04:25:58 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-23 04:25:58 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-23 04:25:58 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-23 04:25:58 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-23 04:25:58 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-23 04:25:58 (9268) [INFO] 
* 2024-12-23 04:25:58 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-23 04:25:58 (9238) [INFO] 
* 2024-12-23 04:25:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 04:25:59 (9251) [INFO] Determining fastest mirrors
* 2024-12-23 04:26:04 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-23 04:26:04 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-23 04:26:04 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-23 04:26:04 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-23 04:26:04 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-23 04:26:05 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 04:26:05 (9251) [INFO] Trying other mirror.
* 2024-12-23 04:26:05 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-23 04:26:05 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-23 04:26:05 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-23 04:26:05 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-23 04:26:05 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-23 04:26:05 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-23 04:26:05 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-23 04:26:05 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-23 04:26:05 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-23 04:26:05 (9251) [INFO]         or
* 2024-12-23 04:26:05 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-23 04:26:05 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-23 04:26:05 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-23 04:26:05 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-23 04:26:05 (9251) [INFO]         compromise:
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-23 04:26:05 (9251) [INFO] 
* 2024-12-23 04:26:05 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-23 04:26:05 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 04:26:05 (9268) [INFO] 
* 2024-12-23 04:26: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-23 04:26:05 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 04:26:05 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-23 04:26:06 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/F_3WgQ37qU/ea_profile.json
* 2024-12-23 04:26: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/F_3WgQ37qU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-23 04:26:09 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-24 04:25:39 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-24 04:25:39 (10313) [INFO] Script is up to date.
* 2024-12-24 04:25:41 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-24 04:25:41 (9238) [INFO] 
* 2024-12-24 04:25:44 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-24 04:25:44 (9238) [INFO] 
* 2024-12-24 04:25:50 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-24 04:25:50 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-24 04:25:50 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-24 04:25:51 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-24 04:25:51 (9238) [INFO] 
* 2024-12-24 04:25:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 04:25:51 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-24 04:25:52 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-24 04:25:52 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-24 04:25:52 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-24 04:25:52 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-24 04:25:52 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-24 04:25:52 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 04:25:52 (9251) [INFO] Trying other mirror.
* 2024-12-24 04:25:52 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-24 04:25:52 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-24 04:25:52 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-24 04:25:52 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-24 04:25:52 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-24 04:25:52 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-24 04:25:52 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-24 04:25:52 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-24 04:25:52 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-24 04:25:52 (9251) [INFO]         or
* 2024-12-24 04:25:52 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-24 04:25:52 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-24 04:25:52 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-24 04:25:52 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-24 04:25:52 (9251) [INFO]         compromise:
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-24 04:25:52 (9251) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-24 04:25:52 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 04:25:52 (9268) [INFO] 
* 2024-12-24 04:25:52 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 04:25:52 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-24 04:25:52 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-24 04:25:52 (9238) [INFO] 
* 2024-12-24 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 04:25:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-24 04:25:53 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-24 04:25:53 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-24 04:25:53 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-24 04:25:53 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-24 04:25:53 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-24 04:25:53 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-24 04:25:53 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-24 04:25:53 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-24 04:25:53 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-24 04:25:53 (9268) [INFO] 
* 2024-12-24 04:25:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-24 04:25:53 (9238) [INFO] 
* 2024-12-24 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 04:25:53 (9251) [INFO] Determining fastest mirrors
* 2024-12-24 04:25:57 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-24 04:25:57 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-24 04:25:57 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-24 04:25:57 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-24 04:25:57 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-24 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 04:25:58 (9251) [INFO] Trying other mirror.
* 2024-12-24 04:25:58 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-24 04:25:58 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-24 04:25:58 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-24 04:25:58 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-24 04:25:58 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-24 04:25:58 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-24 04:25:58 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-24 04:25:58 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-24 04:25:58 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-24 04:25:58 (9251) [INFO]         or
* 2024-12-24 04:25:58 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-24 04:25:58 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-24 04:25:58 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-24 04:25:58 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-24 04:25:58 (9251) [INFO]         compromise:
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-24 04:25:58 (9251) [INFO] 
* 2024-12-24 04:25:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-24 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 04:25:58 (9268) [INFO] 
* 2024-12-24 04:25:58 (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 04:25:58 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 04:25:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-24 04:25:59 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HG_QR1krq6/ea_profile.json
* 2024-12-24 04:26: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/HG_QR1krq6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-24 04:26:00 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-25 04:25:38 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-25 04:25:38 (10313) [INFO] Script is up to date.
* 2024-12-25 04:25:39 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-25 04:25:39 (9238) [INFO] 
* 2024-12-25 04:25:42 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-25 04:25:42 (9238) [INFO] 
* 2024-12-25 04:25:48 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-25 04:25:48 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-25 04:25:48 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-25 04:25:48 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-25 04:25:48 (9238) [INFO] 
* 2024-12-25 04:25:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 04:25:48 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-25 04:25:49 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-25 04:25:49 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-25 04:25:49 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-25 04:25:49 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-25 04:25:49 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-25 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 04:25:49 (9251) [INFO] Trying other mirror.
* 2024-12-25 04:25:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-25 04:25:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-25 04:25:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-25 04:25:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-25 04:25:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-25 04:25:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-25 04:25:49 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-25 04:25:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-25 04:25:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-25 04:25:49 (9251) [INFO]         or
* 2024-12-25 04:25:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-25 04:25:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-25 04:25:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-25 04:25:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-25 04:25:49 (9251) [INFO]         compromise:
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-25 04:25:49 (9251) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-25 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 04:25:49 (9268) [INFO] 
* 2024-12-25 04:25:49 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 04:25:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-25 04:25:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-25 04:25:49 (9238) [INFO] 
* 2024-12-25 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 04:25:50 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-25 04:25:50 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-25 04:25:50 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-25 04:25:50 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-25 04:25:50 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-25 04:25:50 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-25 04:25:50 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-25 04:25:50 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-25 04:25:50 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-25 04:25:50 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-25 04:25:50 (9268) [INFO] 
* 2024-12-25 04:25:50 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-25 04:25:50 (9238) [INFO] 
* 2024-12-25 04:25:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 04:25:50 (9251) [INFO] Determining fastest mirrors
* 2024-12-25 04:25:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-25 04:25:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-25 04:25:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-25 04:25:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-25 04:25:53 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-25 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 04:25:53 (9251) [INFO] Trying other mirror.
* 2024-12-25 04:25:53 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-25 04:25:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-25 04:25:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-25 04:25:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-25 04:25:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-25 04:25:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-25 04:25:53 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-25 04:25:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-25 04:25:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-25 04:25:53 (9251) [INFO]         or
* 2024-12-25 04:25:53 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-25 04:25:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-25 04:25:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-25 04:25:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-25 04:25:53 (9251) [INFO]         compromise:
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-25 04:25:53 (9251) [INFO] 
* 2024-12-25 04:25:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-25 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 04:25:53 (9268) [INFO] 
* 2024-12-25 04:25: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-25 04:25:53 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 04:25:54 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-25 04:25:55 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/puVsZCBbB_/ea_profile.json
* 2024-12-25 04:25: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/puVsZCBbB_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-25 04:25:56 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-26 04:25:41 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-26 04:25:41 (10313) [INFO] Script is up to date.
* 2024-12-26 04:25:42 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-26 04:25:42 (9238) [INFO] 
* 2024-12-26 04:25:45 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-26 04:25:45 (9238) [INFO] 
* 2024-12-26 04:25:52 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-26 04:25:52 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-26 04:25:52 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-26 04:25:52 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-26 04:25:52 (9238) [INFO] 
* 2024-12-26 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 04:25:53 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-26 04:25:54 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-26 04:25:54 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-26 04:25:54 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-26 04:25:54 (9251) [INFO]  * epel: dl.fedoraproject.org
* 2024-12-26 04:25:54 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-26 04:25:55 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 04:25:55 (9251) [INFO] Trying other mirror.
* 2024-12-26 04:25:55 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-26 04:25:55 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-26 04:25:55 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-26 04:25:55 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-26 04:25:55 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-26 04:25:55 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-26 04:25:55 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-26 04:25:55 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-26 04:25:55 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-26 04:25:55 (9251) [INFO]         or
* 2024-12-26 04:25:55 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-26 04:25:55 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-26 04:25:55 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-26 04:25:55 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-26 04:25:55 (9251) [INFO]         compromise:
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-26 04:25:55 (9251) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-26 04:25:55 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 04:25:55 (9268) [INFO] 
* 2024-12-26 04:25:55 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 04:25:55 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-26 04:25:55 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-26 04:25:55 (9238) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 04:25:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-26 04:25:55 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-26 04:25:55 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-26 04:25:55 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-26 04:25:55 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-26 04:25:55 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-26 04:25:55 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-26 04:25:55 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-26 04:25:55 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-26 04:25:55 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-26 04:25:55 (9268) [INFO] 
* 2024-12-26 04:25:55 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-26 04:25:55 (9238) [INFO] 
* 2024-12-26 04:25:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 04:25:55 (9251) [INFO] Determining fastest mirrors
* 2024-12-26 04:25:59 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-26 04:25:59 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-26 04:25:59 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-26 04:25:59 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-26 04:25:59 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-26 04:25:59 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 04:25:59 (9251) [INFO] Trying other mirror.
* 2024-12-26 04:25:59 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-26 04:25:59 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-26 04:25:59 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-26 04:25:59 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-26 04:25:59 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-26 04:25:59 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-26 04:25:59 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-26 04:25:59 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-26 04:25:59 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-26 04:25:59 (9251) [INFO]         or
* 2024-12-26 04:25:59 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-26 04:25:59 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-26 04:25:59 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-26 04:25:59 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-26 04:25:59 (9251) [INFO]         compromise:
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-26 04:25:59 (9251) [INFO] 
* 2024-12-26 04:25:59 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-26 04:25:59 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 04:25:59 (9268) [INFO] 
* 2024-12-26 04:25:59 (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 04:25:59 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 04:26:00 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-26 04:26:01 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iSbsHb0Pew/ea_profile.json
* 2024-12-26 04:26:03 (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/iSbsHb0Pew/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-26 04:26:03 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-27 04:25:39 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-27 04:25:39 (10313) [INFO] Script is up to date.
* 2024-12-27 04:25:40 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-27 04:25:40 (9238) [INFO] 
* 2024-12-27 04:25:42 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-27 04:25:42 (9238) [INFO] 
* 2024-12-27 04:25:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-27 04:25:49 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-27 04:25:49 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-27 04:25:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-27 04:25:49 (9238) [INFO] 
* 2024-12-27 04:25:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 04:25:50 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-27 04:25:51 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-27 04:25:51 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-27 04:25:51 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-27 04:25:51 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-27 04:25:51 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-27 04:25:52 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 04:25:52 (9251) [INFO] Trying other mirror.
* 2024-12-27 04:25:52 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-27 04:25:52 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 04:25:52 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 04:25:52 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-27 04:25:52 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-27 04:25:52 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-27 04:25:52 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 04:25:52 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-27 04:25:52 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-27 04:25:52 (9251) [INFO]         or
* 2024-12-27 04:25:52 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 04:25:52 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 04:25:52 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 04:25:52 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 04:25:52 (9251) [INFO]         compromise:
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-27 04:25:52 (9251) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-27 04:25:52 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 04:25:52 (9268) [INFO] 
* 2024-12-27 04:25:52 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 04:25:52 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-27 04:25:52 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-27 04:25:52 (9238) [INFO] 
* 2024-12-27 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 04:25:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-27 04:25:53 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-27 04:25:53 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-27 04:25:53 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-27 04:25:53 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-27 04:25:53 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-27 04:25:53 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-27 04:25:53 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-27 04:25:53 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-27 04:25:53 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-27 04:25:53 (9268) [INFO] 
* 2024-12-27 04:25:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-27 04:25:53 (9238) [INFO] 
* 2024-12-27 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 04:25:53 (9251) [INFO] Determining fastest mirrors
* 2024-12-27 04:25:57 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-27 04:25:57 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-27 04:25:57 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-27 04:25:57 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-27 04:25:57 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-27 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 04:25:58 (9251) [INFO] Trying other mirror.
* 2024-12-27 04:25:58 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-27 04:25:58 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 04:25:58 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 04:25:58 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-27 04:25:58 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-27 04:25:58 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-27 04:25:58 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 04:25:58 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-27 04:25:58 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-27 04:25:58 (9251) [INFO]         or
* 2024-12-27 04:25:58 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 04:25:58 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 04:25:58 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 04:25:58 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 04:25:58 (9251) [INFO]         compromise:
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-27 04:25:58 (9251) [INFO] 
* 2024-12-27 04:25:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-27 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 04:25:58 (9268) [INFO] 
* 2024-12-27 04:25:58 (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 04:25:58 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 04:25:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-27 04:25:59 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XLH3f75Ikg/ea_profile.json
* 2024-12-27 04:26: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/XLH3f75Ikg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-27 04:26:01 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-28 04:26:26 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-28 04:26:26 (10313) [INFO] Script is up to date.
* 2024-12-28 04:26:28 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-28 04:26:28 (9238) [INFO] 
* 2024-12-28 04:26:31 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-28 04:26:31 (9238) [INFO] 
* 2024-12-28 04:26:38 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-28 04:26:38 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-28 04:26:38 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-28 04:26:38 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-28 04:26:38 (9238) [INFO] 
* 2024-12-28 04:26:38 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 04:26:39 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-28 04:26:39 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-28 04:26:39 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-28 04:26:39 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-28 04:26:39 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-28 04:26:39 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-28 04:26:40 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 04:26:40 (9251) [INFO] Trying other mirror.
* 2024-12-28 04:26:40 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-28 04:26:40 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-28 04:26:40 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-28 04:26:40 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-28 04:26:40 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-28 04:26:40 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-28 04:26:40 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-28 04:26:40 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-28 04:26:40 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-28 04:26:40 (9251) [INFO]         or
* 2024-12-28 04:26:40 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-28 04:26:40 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-28 04:26:40 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-28 04:26:40 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-28 04:26:40 (9251) [INFO]         compromise:
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-28 04:26:40 (9251) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-28 04:26:40 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 04:26:40 (9268) [INFO] 
* 2024-12-28 04:26:40 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 04:26:40 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-28 04:26:40 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-28 04:26:40 (9238) [INFO] 
* 2024-12-28 04:26:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 04:26:40 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-28 04:26:40 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-28 04:26:40 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-28 04:26:40 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-28 04:26:40 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-28 04:26:40 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-28 04:26:40 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-28 04:26:40 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-28 04:26:40 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-28 04:26:40 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-28 04:26:40 (9268) [INFO] 
* 2024-12-28 04:26:40 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-28 04:26:40 (9238) [INFO] 
* 2024-12-28 04:26:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 04:26:41 (9251) [INFO] Determining fastest mirrors
* 2024-12-28 04:26:44 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-28 04:26:44 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-28 04:26:44 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-28 04:26:44 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-28 04:26:44 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-28 04:26:45 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 04:26:45 (9251) [INFO] Trying other mirror.
* 2024-12-28 04:26:45 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-28 04:26:45 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-28 04:26:45 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-28 04:26:45 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-28 04:26:45 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-28 04:26:45 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-28 04:26:45 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-28 04:26:45 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-28 04:26:45 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-28 04:26:45 (9251) [INFO]         or
* 2024-12-28 04:26:45 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-28 04:26:45 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-28 04:26:45 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-28 04:26:45 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-28 04:26:45 (9251) [INFO]         compromise:
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-28 04:26:45 (9251) [INFO] 
* 2024-12-28 04:26:45 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-28 04:26:45 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 04:26:45 (9268) [INFO] 
* 2024-12-28 04:26: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-28 04:26:45 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 04:26:45 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-28 04:26:46 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_uTxzcqTq8/ea_profile.json
* 2024-12-28 04:26: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/_uTxzcqTq8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-28 04:26:47 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-29 04:26:27 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-29 04:26:27 (10313) [INFO] Script is up to date.
* 2024-12-29 04:26:28 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-29 04:26:28 (9238) [INFO] 
* 2024-12-29 04:26:31 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-29 04:26:31 (9238) [INFO] 
* 2024-12-29 04:26:39 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-29 04:26:39 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-29 04:26:39 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-29 04:26:39 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-29 04:26:39 (9238) [INFO] 
* 2024-12-29 04:26:39 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 04:26:39 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-29 04:26:40 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-29 04:26:40 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-29 04:26:40 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-29 04:26:40 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-29 04:26:40 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-29 04:26:41 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 04:26:41 (9251) [INFO] Trying other mirror.
* 2024-12-29 04:26:41 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-29 04:26:41 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-29 04:26:41 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-29 04:26:41 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-29 04:26:41 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-29 04:26:41 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-29 04:26:41 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-29 04:26:41 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-29 04:26:41 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-29 04:26:41 (9251) [INFO]         or
* 2024-12-29 04:26:41 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-29 04:26:41 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-29 04:26:41 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-29 04:26:41 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-29 04:26:41 (9251) [INFO]         compromise:
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-29 04:26:41 (9251) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-29 04:26:41 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 04:26:41 (9268) [INFO] 
* 2024-12-29 04:26:41 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 04:26:41 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-29 04:26:41 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-29 04:26:41 (9238) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 04:26:41 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-29 04:26:41 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-29 04:26:41 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-29 04:26:41 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-29 04:26:41 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-29 04:26:41 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-29 04:26:41 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-29 04:26:41 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-29 04:26:41 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-29 04:26:41 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-29 04:26:41 (9268) [INFO] 
* 2024-12-29 04:26:41 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-29 04:26:41 (9238) [INFO] 
* 2024-12-29 04:26:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 04:26:42 (9251) [INFO] Determining fastest mirrors
* 2024-12-29 04:26:45 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-29 04:26:45 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-29 04:26:45 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-29 04:26:45 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-29 04:26:45 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-29 04:26:45 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 04:26:45 (9251) [INFO] Trying other mirror.
* 2024-12-29 04:26:45 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-29 04:26:45 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-29 04:26:45 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-29 04:26:45 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-29 04:26:45 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-29 04:26:45 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-29 04:26:45 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-29 04:26:45 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-29 04:26:45 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-29 04:26:45 (9251) [INFO]         or
* 2024-12-29 04:26:45 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-29 04:26:45 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-29 04:26:45 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-29 04:26:45 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-29 04:26:45 (9251) [INFO]         compromise:
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-29 04:26:45 (9251) [INFO] 
* 2024-12-29 04:26:45 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-29 04:26:45 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 04:26:45 (9268) [INFO] 
* 2024-12-29 04:26: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-29 04:26:45 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 04:26:46 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-29 04:26:46 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8u7cIFbHL3/ea_profile.json
* 2024-12-29 04:26: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/8u7cIFbHL3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-29 04:26:48 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-30 04:25:40 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-30 04:25:40 (10313) [INFO] Script is up to date.
* 2024-12-30 04:25:41 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-30 04:25:41 (9238) [INFO] 
* 2024-12-30 04:25:44 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-30 04:25:44 (9238) [INFO] 
* 2024-12-30 04:25:59 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-30 04:25:59 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-30 04:25:59 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-30 04:25:59 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-30 04:25:59 (9238) [INFO] 
* 2024-12-30 04:25:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 04:26:00 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-30 04:26:00 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-30 04:26:00 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-30 04:26:00 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-30 04:26:00 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-30 04:26:00 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-30 04:26:01 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 04:26:01 (9251) [INFO] Trying other mirror.
* 2024-12-30 04:26:01 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-30 04:26:01 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-30 04:26:01 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-30 04:26:01 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-30 04:26:01 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-30 04:26:01 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-30 04:26:01 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-30 04:26:01 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-30 04:26:01 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-30 04:26:01 (9251) [INFO]         or
* 2024-12-30 04:26:01 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-30 04:26:01 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-30 04:26:01 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-30 04:26:01 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-30 04:26:01 (9251) [INFO]         compromise:
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-30 04:26:01 (9251) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-30 04:26:01 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 04:26:01 (9268) [INFO] 
* 2024-12-30 04:26:01 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 04:26:01 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-30 04:26:01 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-30 04:26:01 (9238) [INFO] 
* 2024-12-30 04:26:01 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 04:26:02 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-30 04:26:02 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-30 04:26:02 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-30 04:26:02 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-30 04:26:02 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-30 04:26:02 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-30 04:26:02 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-30 04:26:02 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-30 04:26:02 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-30 04:26:02 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-30 04:26:02 (9268) [INFO] 
* 2024-12-30 04:26:02 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-30 04:26:02 (9238) [INFO] 
* 2024-12-30 04:26:02 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 04:26:02 (9251) [INFO] Determining fastest mirrors
* 2024-12-30 04:26:05 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-30 04:26:05 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-30 04:26:05 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-30 04:26:05 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-30 04:26:05 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-30 04:26:06 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 04:26:06 (9251) [INFO] Trying other mirror.
* 2024-12-30 04:26:06 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-30 04:26:06 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-30 04:26:06 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-30 04:26:06 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-30 04:26:06 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-30 04:26:06 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-30 04:26:06 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-30 04:26:06 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-30 04:26:06 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-30 04:26:06 (9251) [INFO]         or
* 2024-12-30 04:26:06 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-30 04:26:06 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-30 04:26:06 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-30 04:26:06 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-30 04:26:06 (9251) [INFO]         compromise:
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-30 04:26:06 (9251) [INFO] 
* 2024-12-30 04:26:06 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-30 04:26:06 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 04:26:06 (9268) [INFO] 
* 2024-12-30 04:26:06 (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 04:26:06 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 04:26:06 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-30 04:26:07 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ps3SNm4cKQ/ea_profile.json
* 2024-12-30 04:26: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/Ps3SNm4cKQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-30 04:26:09 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-31 04:25:49 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-31 04:25:49 (10313) [INFO] Script is up to date.
* 2024-12-31 04:25:50 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-31 04:25:50 (9238) [INFO] 
* 2024-12-31 04:25:53 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-31 04:25:53 (9238) [INFO] 
* 2024-12-31 04:26:00 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2024-12-31 04:26:00 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2024-12-31 04:26:00 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2024-12-31 04:26:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-31 04:26:00 (9238) [INFO] 
* 2024-12-31 04:26:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 04:26:01 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-31 04:26:01 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-31 04:26:01 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-31 04:26:01 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-31 04:26:01 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-31 04:26:01 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-31 04:26:02 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 04:26:02 (9251) [INFO] Trying other mirror.
* 2024-12-31 04:26:02 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-31 04:26:02 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-31 04:26:02 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-31 04:26:02 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-31 04:26:02 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-31 04:26:02 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-31 04:26:02 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-31 04:26:02 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-31 04:26:02 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-31 04:26:02 (9251) [INFO]         or
* 2024-12-31 04:26:02 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-31 04:26:02 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-31 04:26:02 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-31 04:26:02 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-31 04:26:02 (9251) [INFO]         compromise:
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-31 04:26:02 (9251) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-31 04:26:02 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 04:26:02 (9268) [INFO] 
* 2024-12-31 04:26:02 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 04:26:02 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-31 04:26:02 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-31 04:26:02 (9238) [INFO] 
* 2024-12-31 04:26:02 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 04:26:02 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-12-31 04:26:02 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-31 04:26:02 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-31 04:26:02 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2024-12-31 04:26:02 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-12-31 04:26:02 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-12-31 04:26:02 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2024-12-31 04:26:02 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2024-12-31 04:26:02 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-31 04:26:02 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2024-12-31 04:26:02 (9268) [INFO] 
* 2024-12-31 04:26:02 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-31 04:26:02 (9238) [INFO] 
* 2024-12-31 04:26:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 04:26:03 (9251) [INFO] Determining fastest mirrors
* 2024-12-31 04:26:06 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-31 04:26:06 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-31 04:26:06 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-31 04:26:06 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-31 04:26:06 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-31 04:26:07 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 04:26:07 (9251) [INFO] Trying other mirror.
* 2024-12-31 04:26:07 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2024-12-31 04:26:07 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-31 04:26:07 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-31 04:26:07 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-31 04:26:07 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-31 04:26:07 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-31 04:26:07 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-31 04:26:07 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-31 04:26:07 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-31 04:26:07 (9251) [INFO]         or
* 2024-12-31 04:26:07 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-31 04:26:07 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-31 04:26:07 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-31 04:26:07 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-31 04:26:07 (9251) [INFO]         compromise:
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-31 04:26:07 (9251) [INFO] 
* 2024-12-31 04:26:07 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-31 04:26:07 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 04:26:07 (9268) [INFO] 
* 2024-12-31 04:26: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-31 04:26:07 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 04:26:07 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-31 04:26:08 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/euZEhOjTHL/ea_profile.json
* 2024-12-31 04:26: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/euZEhOjTHL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-31 04:26:10 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-01 04:25:38 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-01 04:25:38 (10313) [INFO] Script is up to date.
* 2025-01-01 04:25:39 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-01 04:25:39 (9238) [INFO] 
* 2025-01-01 04:25:42 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-01 04:25:42 (9238) [INFO] 
* 2025-01-01 04:25:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-01 04:25:49 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-01 04:25:49 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-01 04:25:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-01 04:25:49 (9238) [INFO] 
* 2025-01-01 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 04:25:50 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-01 04:25:51 (9251) [INFO]  * EA4: 63.247.64.58
* 2025-01-01 04:25:51 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-01-01 04:25:51 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-01-01 04:25:51 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-01 04:25:51 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-01 04:25:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 04:25:51 (9251) [INFO] Trying other mirror.
* 2025-01-01 04:25:51 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-01 04:25:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-01 04:25:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-01 04:25:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-01 04:25:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-01 04:25:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-01 04:25:51 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-01 04:25:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-01 04:25:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-01 04:25:51 (9251) [INFO]         or
* 2025-01-01 04:25:51 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-01 04:25:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-01 04:25:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-01 04:25:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-01 04:25:51 (9251) [INFO]         compromise:
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-01 04:25:51 (9251) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-01 04:25:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 04:25:51 (9268) [INFO] 
* 2025-01-01 04:25:51 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 04:25:51 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-01 04:25:51 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-01 04:25:51 (9238) [INFO] 
* 2025-01-01 04:25:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 04:25:52 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-01 04:25:52 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-01 04:25:52 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-01 04:25:52 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-01 04:25:52 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-01 04:25:52 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-01 04:25:52 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-01 04:25:52 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-01 04:25:52 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-01 04:25:52 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-01 04:25:52 (9268) [INFO] 
* 2025-01-01 04:25:52 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-01 04:25:52 (9238) [INFO] 
* 2025-01-01 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 04:25:52 (9251) [INFO] Determining fastest mirrors
* 2025-01-01 04:25:55 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-01 04:25:55 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-01 04:25:55 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-01 04:25:55 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-01 04:25:55 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-01 04:25:56 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 04:25:56 (9251) [INFO] Trying other mirror.
* 2025-01-01 04:25:56 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-01 04:25:56 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-01 04:25:56 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-01 04:25:56 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-01 04:25:56 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-01 04:25:56 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-01 04:25:56 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-01 04:25:56 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-01 04:25:56 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-01 04:25:56 (9251) [INFO]         or
* 2025-01-01 04:25:56 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-01 04:25:56 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-01 04:25:56 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-01 04:25:56 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-01 04:25:56 (9251) [INFO]         compromise:
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-01 04:25:56 (9251) [INFO] 
* 2025-01-01 04:25:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-01 04:25:56 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 04:25:56 (9268) [INFO] 
* 2025-01-01 04:25: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-01 04:25:56 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 04:25:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-01 04:25:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cUejsj3SkI/ea_profile.json
* 2025-01-01 04:25: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/cUejsj3SkI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-01 04:25:59 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-02 04:25:33 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-02 04:25:33 (10313) [INFO] Script is up to date.
* 2025-01-02 04:25:35 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-02 04:25:35 (9238) [INFO] 
* 2025-01-02 04:25:38 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-02 04:25:38 (9238) [INFO] 
* 2025-01-02 04:25:44 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-02 04:25:44 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-02 04:25:44 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-02 04:25:44 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-02 04:25:44 (9238) [INFO] 
* 2025-01-02 04:25:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 04:25:44 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-02 04:25:46 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-02 04:25:46 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-02 04:25:46 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-02 04:25:46 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-02 04:25:46 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-02 04:25:46 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 04:25:46 (9251) [INFO] Trying other mirror.
* 2025-01-02 04:25:46 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-02 04:25:46 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-02 04:25:46 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-02 04:25:46 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-02 04:25:46 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-02 04:25:46 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-02 04:25:46 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-02 04:25:46 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-02 04:25:46 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-02 04:25:46 (9251) [INFO]         or
* 2025-01-02 04:25:46 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-02 04:25:46 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-02 04:25:46 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-02 04:25:46 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-02 04:25:46 (9251) [INFO]         compromise:
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-02 04:25:46 (9251) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-02 04:25:46 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 04:25:46 (9268) [INFO] 
* 2025-01-02 04:25:46 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 04:25:46 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-02 04:25:46 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-02 04:25:46 (9238) [INFO] 
* 2025-01-02 04:25:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 04:25:47 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-02 04:25:47 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-02 04:25:47 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-02 04:25:47 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-02 04:25:47 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-02 04:25:47 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-02 04:25:47 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-02 04:25:47 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-02 04:25:47 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-02 04:25:47 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-02 04:25:47 (9268) [INFO] 
* 2025-01-02 04:25:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-02 04:25:47 (9238) [INFO] 
* 2025-01-02 04:25:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 04:25:47 (9251) [INFO] Determining fastest mirrors
* 2025-01-02 04:25:50 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-02 04:25:50 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-02 04:25:50 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-02 04:25:50 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-02 04:25:50 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-02 04:25:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 04:25:51 (9251) [INFO] Trying other mirror.
* 2025-01-02 04:25:51 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-02 04:25:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-02 04:25:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-02 04:25:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-02 04:25:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-02 04:25:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-02 04:25:51 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-02 04:25:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-02 04:25:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-02 04:25:51 (9251) [INFO]         or
* 2025-01-02 04:25:51 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-02 04:25:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-02 04:25:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-02 04:25:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-02 04:25:51 (9251) [INFO]         compromise:
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-02 04:25:51 (9251) [INFO] 
* 2025-01-02 04:25:51 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-02 04:25:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 04:25:51 (9268) [INFO] 
* 2025-01-02 04:25: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-02 04:25:51 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 04:25:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-02 04:25:52 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pKPseHzxcB/ea_profile.json
* 2025-01-02 04:25: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/pKPseHzxcB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-02 04:25:54 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-03 04:25:39 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-03 04:25:39 (10313) [INFO] Script is up to date.
* 2025-01-03 04:25:41 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-03 04:25:41 (9238) [INFO] 
* 2025-01-03 04:25:43 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-03 04:25:43 (9238) [INFO] 
* 2025-01-03 04:25:51 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-03 04:25:51 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-03 04:25:51 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-03 04:25:51 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-03 04:25:51 (9238) [INFO] 
* 2025-01-03 04:25:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 04:25:51 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-03 04:25:52 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-03 04:25:52 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-03 04:25:52 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-03 04:25:52 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-03 04:25:52 (9251) [INFO]  * remi-safe: muug.ca
* 2025-01-03 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 04:25:53 (9251) [INFO] Trying other mirror.
* 2025-01-03 04:25:53 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-03 04:25:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 04:25:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 04:25:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-03 04:25:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-03 04:25:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-03 04:25:53 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 04:25:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-03 04:25:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-03 04:25:53 (9251) [INFO]         or
* 2025-01-03 04:25:53 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 04:25:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 04:25:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 04:25:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 04:25:53 (9251) [INFO]         compromise:
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-03 04:25:53 (9251) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-03 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 04:25:53 (9268) [INFO] 
* 2025-01-03 04:25:53 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 04:25:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-03 04:25:53 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-03 04:25:53 (9238) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 04:25:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-03 04:25:53 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-03 04:25:53 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-03 04:25:53 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-03 04:25:53 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-03 04:25:53 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-03 04:25:53 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-03 04:25:53 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-03 04:25:53 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-03 04:25:53 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-03 04:25:53 (9268) [INFO] 
* 2025-01-03 04:25:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-03 04:25:53 (9238) [INFO] 
* 2025-01-03 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 04:25:54 (9251) [INFO] Determining fastest mirrors
* 2025-01-03 04:25:57 (9251) [INFO]  * EA4: 63.247.64.58
* 2025-01-03 04:25:57 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-01-03 04:25:57 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-01-03 04:25:57 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-03 04:25:57 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-03 04:25:57 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 04:25:57 (9251) [INFO] Trying other mirror.
* 2025-01-03 04:25:57 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-03 04:25:57 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 04:25:57 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 04:25:57 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-03 04:25:57 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-03 04:25:57 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-03 04:25:57 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 04:25:57 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-03 04:25:57 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-03 04:25:57 (9251) [INFO]         or
* 2025-01-03 04:25:57 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 04:25:57 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 04:25:57 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 04:25:57 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 04:25:57 (9251) [INFO]         compromise:
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-03 04:25:57 (9251) [INFO] 
* 2025-01-03 04:25:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-03 04:25:57 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 04:25:57 (9268) [INFO] 
* 2025-01-03 04:25:57 (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 04:25:57 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 04:25:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-03 04:25:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jwU7KUuwbF/ea_profile.json
* 2025-01-03 04:26: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/jwU7KUuwbF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-03 04:26:00 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-04 04:26:34 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-04 04:26:34 (10313) [INFO] Script is up to date.
* 2025-01-04 04:26:35 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-04 04:26:35 (9238) [INFO] 
* 2025-01-04 04:26:39 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-04 04:26:39 (9238) [INFO] 
* 2025-01-04 04:26:47 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-04 04:26:47 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-04 04:26:47 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-04 04:26:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-04 04:26:47 (9238) [INFO] 
* 2025-01-04 04:26:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 04:26:47 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-04 04:26:48 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-04 04:26:48 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-04 04:26:48 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-04 04:26:48 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-04 04:26:48 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-04 04:26:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 04:26:49 (9251) [INFO] Trying other mirror.
* 2025-01-04 04:26:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-04 04:26:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-04 04:26:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-04 04:26:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-04 04:26:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-04 04:26:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-04 04:26:49 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-04 04:26:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-04 04:26:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-04 04:26:49 (9251) [INFO]         or
* 2025-01-04 04:26:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-04 04:26:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-04 04:26:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-04 04:26:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-04 04:26:49 (9251) [INFO]         compromise:
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-04 04:26:49 (9251) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-04 04:26:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 04:26:49 (9268) [INFO] 
* 2025-01-04 04:26:49 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 04:26:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-04 04:26:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-04 04:26:49 (9238) [INFO] 
* 2025-01-04 04:26:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 04:26:49 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-04 04:26:49 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-04 04:26:49 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-04 04:26:49 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-04 04:26:49 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-04 04:26:49 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-04 04:26:49 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-04 04:26:49 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-04 04:26:49 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-04 04:26:49 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-04 04:26:49 (9268) [INFO] 
* 2025-01-04 04:26:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-04 04:26:49 (9238) [INFO] 
* 2025-01-04 04:26:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 04:26:50 (9251) [INFO] Determining fastest mirrors
* 2025-01-04 04:26:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-04 04:26:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-04 04:26:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-04 04:26:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-04 04:26:53 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-04 04:26:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 04:26:54 (9251) [INFO] Trying other mirror.
* 2025-01-04 04:26:54 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-04 04:26:54 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-04 04:26:54 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-04 04:26:54 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-04 04:26:54 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-04 04:26:54 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-04 04:26:54 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-04 04:26:54 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-04 04:26:54 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-04 04:26:54 (9251) [INFO]         or
* 2025-01-04 04:26:54 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-04 04:26:54 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-04 04:26:54 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-04 04:26:54 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-04 04:26:54 (9251) [INFO]         compromise:
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-04 04:26:54 (9251) [INFO] 
* 2025-01-04 04:26:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-04 04:26:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 04:26:54 (9268) [INFO] 
* 2025-01-04 04:26:54 (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 04:26:54 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 04:26:54 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-04 04:26:55 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uF1t2sGcj9/ea_profile.json
* 2025-01-04 04:26: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/uF1t2sGcj9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-04 04:26:57 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-05 04:26:28 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-05 04:26:28 (10313) [INFO] Script is up to date.
* 2025-01-05 04:26:29 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-05 04:26:29 (9238) [INFO] 
* 2025-01-05 04:26:32 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-05 04:26:32 (9238) [INFO] 
* 2025-01-05 04:26:45 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-05 04:26:45 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-05 04:26:45 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-05 04:26:45 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-05 04:26:45 (9238) [INFO] 
* 2025-01-05 04:26:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 04:26:45 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-05 04:26:46 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-05 04:26:46 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-05 04:26:46 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-05 04:26:46 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-05 04:26:46 (9251) [INFO]  * remi-safe: muug.ca
* 2025-01-05 04:26:46 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 04:26:46 (9251) [INFO] Trying other mirror.
* 2025-01-05 04:26:46 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-05 04:26:46 (9251) [INFO] 
* 2025-01-05 04:26:46 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-05 04:26:46 (9251) [INFO] 
* 2025-01-05 04:26:46 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-05 04:26:46 (9251) [INFO] 
* 2025-01-05 04:26:46 (9251) [INFO] 
* 2025-01-05 04:26:46 (9251) [INFO] 
* 2025-01-05 04:26:46 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-05 04:26:47 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-05 04:26:47 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-05 04:26:47 (9251) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-05 04:26:47 (9251) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-05 04:26:47 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-05 04:26:47 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-05 04:26:47 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-05 04:26:47 (9251) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-05 04:26:47 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-05 04:26:47 (9251) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-05 04:26:47 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-05 04:26:47 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-05 04:26:47 (9251) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-05 04:26:47 (9251) [INFO]         or
* 2025-01-05 04:26:47 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-05 04:26:47 (9251) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-05 04:26:47 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-05 04:26:47 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-05 04:26:47 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-05 04:26:47 (9251) [INFO]         compromise:
* 2025-01-05 04:26:47 (9251) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-05 04:26:47 (9251) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-05 04:26:47 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 04:26:47 (9268) [INFO] 
* 2025-01-05 04:26:47 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 04:26:47 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-05 04:26:47 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-05 04:26:47 (9238) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 04:26:47 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-05 04:26:47 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-05 04:26:47 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-05 04:26:47 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-05 04:26:47 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-05 04:26:47 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-05 04:26:47 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-05 04:26:47 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-05 04:26:47 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-05 04:26:47 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-05 04:26:47 (9268) [INFO] 
* 2025-01-05 04:26:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-05 04:26:47 (9238) [INFO] 
* 2025-01-05 04:26:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 04:26:47 (9251) [INFO] Determining fastest mirrors
* 2025-01-05 04:26:50 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-05 04:26:50 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-05 04:26:50 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-05 04:26:50 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-05 04:26:50 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-05 04:26:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 04:26:51 (9251) [INFO] Trying other mirror.
* 2025-01-05 04:26:51 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-05 04:26:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-05 04:26:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-05 04:26:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-05 04:26:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-05 04:26:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-05 04:26:51 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-05 04:26:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-05 04:26:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-05 04:26:51 (9251) [INFO]         or
* 2025-01-05 04:26:51 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-05 04:26:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-05 04:26:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-05 04:26:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-05 04:26:51 (9251) [INFO]         compromise:
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-05 04:26:51 (9251) [INFO] 
* 2025-01-05 04:26:51 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-05 04:26:51 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 04:26:51 (9268) [INFO] 
* 2025-01-05 04:26: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-05 04:26:51 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 04:26:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-05 04:26:52 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qO_zbzuVn3/ea_profile.json
* 2025-01-05 04:26: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/qO_zbzuVn3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-05 04:26:54 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-06 04:25:40 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-06 04:25:41 (10313) [INFO] Script is up to date.
* 2025-01-06 04:25:42 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-06 04:25:42 (9238) [INFO] 
* 2025-01-06 04:25:44 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-06 04:25:44 (9238) [INFO] 
* 2025-01-06 04:25:51 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-06 04:25:51 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-06 04:25:51 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-06 04:25:51 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-06 04:25:51 (9238) [INFO] 
* 2025-01-06 04:25:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 04:25:52 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-06 04:25:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-06 04:25:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-06 04:25:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-06 04:25:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-06 04:25:53 (9251) [INFO]  * remi-safe: muug.ca
* 2025-01-06 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 04:25:54 (9251) [INFO] Trying other mirror.
* 2025-01-06 04:25:54 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-06 04:25:54 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-06 04:25:54 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-06 04:25:54 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-06 04:25:54 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-06 04:25:54 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-06 04:25:54 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-06 04:25:54 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-06 04:25:54 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-06 04:25:54 (9251) [INFO]         or
* 2025-01-06 04:25:54 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-06 04:25:54 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-06 04:25:54 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-06 04:25:54 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-06 04:25:54 (9251) [INFO]         compromise:
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-06 04:25:54 (9251) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-06 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 04:25:54 (9268) [INFO] 
* 2025-01-06 04:25:54 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 04:25:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-06 04:25:54 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-06 04:25:54 (9238) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 04:25:54 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-06 04:25:54 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-06 04:25:54 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-06 04:25:54 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-06 04:25:54 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-06 04:25:54 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-06 04:25:54 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-06 04:25:54 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-06 04:25:54 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-06 04:25:54 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-06 04:25:54 (9268) [INFO] 
* 2025-01-06 04:25:54 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-06 04:25:54 (9238) [INFO] 
* 2025-01-06 04:25:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 04:25:55 (9251) [INFO] Determining fastest mirrors
* 2025-01-06 04:25:58 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-06 04:25:58 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-06 04:25:58 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-06 04:25:58 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-06 04:25:58 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-06 04:25:59 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 04:25:59 (9251) [INFO] Trying other mirror.
* 2025-01-06 04:25:59 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-06 04:25:59 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-06 04:25:59 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-06 04:25:59 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-06 04:25:59 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-06 04:25:59 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-06 04:25:59 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-06 04:25:59 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-06 04:25:59 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-06 04:25:59 (9251) [INFO]         or
* 2025-01-06 04:25:59 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-06 04:25:59 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-06 04:25:59 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-06 04:25:59 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-06 04:25:59 (9251) [INFO]         compromise:
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-06 04:25:59 (9251) [INFO] 
* 2025-01-06 04:25:59 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-06 04:25:59 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 04:25:59 (9268) [INFO] 
* 2025-01-06 04:25:59 (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 04:25:59 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 04:25:59 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-06 04:26:00 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zm4mF7lyD_/ea_profile.json
* 2025-01-06 04:26:03 (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/zm4mF7lyD_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-06 04:26:03 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-07 04:25:40 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-07 04:25:41 (10313) [INFO] Script is up to date.
* 2025-01-07 04:25:42 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-07 04:25:42 (9238) [INFO] 
* 2025-01-07 04:25:45 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-07 04:25:45 (9238) [INFO] 
* 2025-01-07 04:25:52 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-07 04:25:52 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-07 04:25:52 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-07 04:25:52 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-07 04:25:52 (9238) [INFO] 
* 2025-01-07 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 04:25:52 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-07 04:25:54 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-07 04:25:54 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-07 04:25:54 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-07 04:25:54 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-07 04:25:54 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-07 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 04:25:54 (9251) [INFO] Trying other mirror.
* 2025-01-07 04:25:54 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-07 04:25:54 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-07 04:25:54 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-07 04:25:54 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-07 04:25:54 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-07 04:25:54 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-07 04:25:54 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-07 04:25:54 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-07 04:25:54 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-07 04:25:54 (9251) [INFO]         or
* 2025-01-07 04:25:54 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-07 04:25:54 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-07 04:25:54 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-07 04:25:54 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-07 04:25:54 (9251) [INFO]         compromise:
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-07 04:25:54 (9251) [INFO] 
* 2025-01-07 04:25:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-07 04:25:54 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 04:25:54 (9268) [INFO] 
* 2025-01-07 04:25:54 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 04:25:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-07 04:25:54 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-07 04:25:54 (9238) [INFO] 
* 2025-01-07 04:25:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 04:25:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-07 04:25:55 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-07 04:25:55 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-07 04:25:55 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-07 04:25:55 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-07 04:25:55 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-07 04:25:55 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-07 04:25:55 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-07 04:25:55 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-07 04:25:55 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-07 04:25:55 (9268) [INFO] 
* 2025-01-07 04:25:55 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-07 04:25:55 (9238) [INFO] 
* 2025-01-07 04:25:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 04:25:55 (9251) [INFO] Determining fastest mirrors
* 2025-01-07 04:25:59 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-07 04:25:59 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-07 04:25:59 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-07 04:25:59 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-07 04:25:59 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-07 04:26:00 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 04:26:00 (9251) [INFO] Trying other mirror.
* 2025-01-07 04:26:00 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-07 04:26:00 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-07 04:26:00 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-07 04:26:00 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-07 04:26:00 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-07 04:26:00 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-07 04:26:00 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-07 04:26:00 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-07 04:26:00 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-07 04:26:00 (9251) [INFO]         or
* 2025-01-07 04:26:00 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-07 04:26:00 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-07 04:26:00 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-07 04:26:00 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-07 04:26:00 (9251) [INFO]         compromise:
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-07 04:26:00 (9251) [INFO] 
* 2025-01-07 04:26:00 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-07 04:26:00 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 04:26:00 (9268) [INFO] 
* 2025-01-07 04:26:00 (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 04:26:00 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 04:26:00 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-07 04:26:01 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/U6uL0oaXg2/ea_profile.json
* 2025-01-07 04:26:03 (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/U6uL0oaXg2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-07 04:26:03 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-08 04:25:36 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-08 04:25:36 (10313) [INFO] Script is up to date.
* 2025-01-08 04:25:37 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-08 04:25:37 (9238) [INFO] 
* 2025-01-08 04:25:40 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-08 04:25:40 (9238) [INFO] 
* 2025-01-08 04:25:47 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-08 04:25:47 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-08 04:25:47 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-08 04:25:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-08 04:25:47 (9238) [INFO] 
* 2025-01-08 04:25:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 04:25:47 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-08 04:25:48 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-08 04:25:48 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-08 04:25:48 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-08 04:25:48 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-08 04:25:48 (9251) [INFO]  * remi-safe: muug.ca
* 2025-01-08 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 04:25:49 (9251) [INFO] Trying other mirror.
* 2025-01-08 04:25:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-08 04:25:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-08 04:25:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-08 04:25:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-08 04:25:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-08 04:25:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-08 04:25:49 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-08 04:25:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-08 04:25:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-08 04:25:49 (9251) [INFO]         or
* 2025-01-08 04:25:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-08 04:25:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-08 04:25:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-08 04:25:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-08 04:25:49 (9251) [INFO]         compromise:
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-08 04:25:49 (9251) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-08 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 04:25:49 (9268) [INFO] 
* 2025-01-08 04:25:49 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 04:25:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-08 04:25:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-08 04:25:49 (9238) [INFO] 
* 2025-01-08 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 04:25:49 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-08 04:25:49 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-08 04:25:49 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-08 04:25:49 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-08 04:25:49 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-08 04:25:49 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-08 04:25:49 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-08 04:25:49 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-08 04:25:49 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-08 04:25:49 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-08 04:25:49 (9268) [INFO] 
* 2025-01-08 04:25:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-08 04:25:49 (9238) [INFO] 
* 2025-01-08 04:25:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 04:25:50 (9251) [INFO] Determining fastest mirrors
* 2025-01-08 04:25:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-08 04:25:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-08 04:25:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-08 04:25:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-08 04:25:53 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-08 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 04:25:53 (9251) [INFO] Trying other mirror.
* 2025-01-08 04:25:53 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-08 04:25:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-08 04:25:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-08 04:25:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-08 04:25:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-08 04:25:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-08 04:25:53 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-08 04:25:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-08 04:25:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-08 04:25:53 (9251) [INFO]         or
* 2025-01-08 04:25:53 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-08 04:25:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-08 04:25:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-08 04:25:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-08 04:25:53 (9251) [INFO]         compromise:
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-08 04:25:53 (9251) [INFO] 
* 2025-01-08 04:25:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-08 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 04:25:54 (9268) [INFO] 
* 2025-01-08 04:25:54 (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 04:25:54 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 04:25:54 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-08 04:25:55 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Hn3znNODuB/ea_profile.json
* 2025-01-08 04:25: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/Hn3znNODuB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-08 04:25:56 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-09 04:25:34 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-09 04:25:34 (10313) [INFO] Script is up to date.
* 2025-01-09 04:25:35 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-09 04:25:35 (9238) [INFO] 
* 2025-01-09 04:25:39 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-09 04:25:39 (9238) [INFO] 
* 2025-01-09 04:25:46 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-09 04:25:46 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-09 04:25:46 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-09 04:25:46 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-09 04:25:46 (9238) [INFO] 
* 2025-01-09 04:25:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 04:25:46 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-09 04:25:48 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-09 04:25:48 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-09 04:25:48 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-09 04:25:48 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-09 04:25:48 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-09 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 04:25:49 (9251) [INFO] Trying other mirror.
* 2025-01-09 04:25:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-09 04:25:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-09 04:25:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-09 04:25:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-09 04:25:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-09 04:25:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-09 04:25:49 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-09 04:25:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-09 04:25:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-09 04:25:49 (9251) [INFO]         or
* 2025-01-09 04:25:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-09 04:25:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-09 04:25:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-09 04:25:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-09 04:25:49 (9251) [INFO]         compromise:
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-09 04:25:49 (9251) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-09 04:25:49 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 04:25:49 (9268) [INFO] 
* 2025-01-09 04:25:49 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 04:25:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-09 04:25:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-09 04:25:49 (9238) [INFO] 
* 2025-01-09 04:25:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 04:25:49 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-09 04:25:49 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-09 04:25:49 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-09 04:25:49 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-09 04:25:49 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-09 04:25:49 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-09 04:25:49 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-09 04:25:49 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-09 04:25:49 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-09 04:25:49 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-09 04:25:49 (9268) [INFO] 
* 2025-01-09 04:25:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-09 04:25:49 (9238) [INFO] 
* 2025-01-09 04:25:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 04:25:50 (9251) [INFO] Determining fastest mirrors
* 2025-01-09 04:25:55 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-09 04:25:55 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-09 04:25:55 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-09 04:25:55 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-09 04:25:55 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-09 04:25:56 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 04:25:56 (9251) [INFO] Trying other mirror.
* 2025-01-09 04:25:56 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-09 04:25:56 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-09 04:25:56 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-09 04:25:56 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-09 04:25:56 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-09 04:25:56 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-09 04:25:56 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-09 04:25:56 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-09 04:25:56 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-09 04:25:56 (9251) [INFO]         or
* 2025-01-09 04:25:56 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-09 04:25:56 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-09 04:25:56 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-09 04:25:56 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-09 04:25:56 (9251) [INFO]         compromise:
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-09 04:25:56 (9251) [INFO] 
* 2025-01-09 04:25:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-09 04:25:56 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 04:25:56 (9268) [INFO] 
* 2025-01-09 04:25: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-09 04:25:56 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 04:25:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-09 04:25:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cFKUQy_chH/ea_profile.json
* 2025-01-09 04:25: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/cFKUQy_chH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-09 04:25:59 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-10 04:25:37 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-10 04:25:37 (10313) [INFO] Script is up to date.
* 2025-01-10 04:25:39 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-10 04:25:39 (9238) [INFO] 
* 2025-01-10 04:25:43 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-10 04:25:43 (9238) [INFO] 
* 2025-01-10 04:25:50 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-10 04:25:50 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-10 04:25:50 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-10 04:25:50 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-10 04:25:50 (9238) [INFO] 
* 2025-01-10 04:25:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 04:25:50 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-10 04:25:52 (9251) [INFO]  * EA4: 63.247.64.58
* 2025-01-10 04:25:52 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-01-10 04:25:52 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-01-10 04:25:52 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-10 04:25:52 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-10 04:25:52 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 04:25:52 (9251) [INFO] Trying other mirror.
* 2025-01-10 04:25:52 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-10 04:25:52 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 04:25:52 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 04:25:52 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-10 04:25:52 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-10 04:25:52 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-10 04:25:52 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 04:25:52 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-10 04:25:52 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-10 04:25:52 (9251) [INFO]         or
* 2025-01-10 04:25:52 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 04:25:52 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 04:25:52 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 04:25:52 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 04:25:52 (9251) [INFO]         compromise:
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-10 04:25:52 (9251) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-10 04:25:52 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 04:25:52 (9268) [INFO] 
* 2025-01-10 04:25:52 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 04:25:52 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-10 04:25:52 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-10 04:25:52 (9238) [INFO] 
* 2025-01-10 04:25:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 04:25:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-10 04:25:53 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-10 04:25:53 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-10 04:25:53 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-10 04:25:53 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-10 04:25:53 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-10 04:25:53 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-10 04:25:53 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-10 04:25:53 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-10 04:25:53 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-10 04:25:53 (9268) [INFO] 
* 2025-01-10 04:25:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-10 04:25:53 (9238) [INFO] 
* 2025-01-10 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 04:25:53 (9251) [INFO] Determining fastest mirrors
* 2025-01-10 04:25:57 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-10 04:25:57 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-10 04:25:57 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-10 04:25:57 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-10 04:25:57 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-10 04:25:57 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 04:25:57 (9251) [INFO] Trying other mirror.
* 2025-01-10 04:25:57 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-10 04:25:57 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 04:25:57 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 04:25:57 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-10 04:25:57 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-10 04:25:57 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-10 04:25:57 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 04:25:57 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-10 04:25:57 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-10 04:25:57 (9251) [INFO]         or
* 2025-01-10 04:25:57 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 04:25:57 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 04:25:57 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 04:25:57 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 04:25:57 (9251) [INFO]         compromise:
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-10 04:25:57 (9251) [INFO] 
* 2025-01-10 04:25:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-10 04:25:57 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 04:25:57 (9268) [INFO] 
* 2025-01-10 04:25:57 (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 04:25:57 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 04:25:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-10 04:25:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/d6vD4J67qu/ea_profile.json
* 2025-01-10 04:26: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/d6vD4J67qu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-10 04:26:01 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-11 04:26:26 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-11 04:26:26 (10313) [INFO] Script is up to date.
* 2025-01-11 04:26:28 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-11 04:26:28 (9238) [INFO] 
* 2025-01-11 04:26:31 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-11 04:26:31 (9238) [INFO] 
* 2025-01-11 04:26:37 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-11 04:26:37 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-11 04:26:37 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-11 04:26:37 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-11 04:26:37 (9238) [INFO] 
* 2025-01-11 04:26:38 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 04:26:38 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-11 04:26:39 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-11 04:26:39 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-11 04:26:39 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-11 04:26:39 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-11 04:26:39 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-11 04:26:39 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 04:26:39 (9251) [INFO] Trying other mirror.
* 2025-01-11 04:26:39 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-11 04:26:39 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-11 04:26:39 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-11 04:26:39 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-11 04:26:39 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-11 04:26:39 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-11 04:26:39 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-11 04:26:39 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-11 04:26:39 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-11 04:26:39 (9251) [INFO]         or
* 2025-01-11 04:26:39 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-11 04:26:39 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-11 04:26:39 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-11 04:26:39 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-11 04:26:39 (9251) [INFO]         compromise:
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-11 04:26:39 (9251) [INFO] 
* 2025-01-11 04:26:39 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-11 04:26:39 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 04:26:39 (9268) [INFO] 
* 2025-01-11 04:26:39 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 04:26:39 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-11 04:26:39 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-11 04:26:39 (9238) [INFO] 
* 2025-01-11 04:26:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 04:26:40 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-11 04:26:40 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-11 04:26:40 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-11 04:26:40 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-11 04:26:40 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-11 04:26:40 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-11 04:26:40 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-11 04:26:40 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-11 04:26:40 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-11 04:26:40 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-11 04:26:40 (9268) [INFO] 
* 2025-01-11 04:26:40 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-11 04:26:40 (9238) [INFO] 
* 2025-01-11 04:26:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 04:26:40 (9251) [INFO] Determining fastest mirrors
* 2025-01-11 04:26:43 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-11 04:26:43 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-11 04:26:43 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-11 04:26:43 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-11 04:26:43 (9251) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-11 04:26:44 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 04:26:44 (9251) [INFO] Trying other mirror.
* 2025-01-11 04:26:44 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-11 04:26:44 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-11 04:26:44 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-11 04:26:44 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-11 04:26:44 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-11 04:26:44 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-11 04:26:44 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-11 04:26:44 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-11 04:26:44 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-11 04:26:44 (9251) [INFO]         or
* 2025-01-11 04:26:44 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-11 04:26:44 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-11 04:26:44 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-11 04:26:44 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-11 04:26:44 (9251) [INFO]         compromise:
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-11 04:26:44 (9251) [INFO] 
* 2025-01-11 04:26:44 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-11 04:26:44 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 04:26:44 (9268) [INFO] 
* 2025-01-11 04:26: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-11 04:26:44 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 04:26:44 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-11 04:26:45 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ylEP8AfkzP/ea_profile.json
* 2025-01-11 04:26: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/ylEP8AfkzP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-11 04:26:47 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-12 04:26:14 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-12 04:26:14 (10313) [INFO] Script is up to date.
* 2025-01-12 04:26:16 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-12 04:26:16 (9238) [INFO] 
* 2025-01-12 04:26:20 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-12 04:26:20 (9238) [INFO] 
* 2025-01-12 04:26:27 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-12 04:26:27 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-12 04:26:27 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-12 04:26:27 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-12 04:26:27 (9238) [INFO] 
* 2025-01-12 04:26:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 04:26:27 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-12 04:26:28 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-12 04:26:28 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-12 04:26:28 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-12 04:26:28 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-12 04:26:28 (9251) [INFO]  * remi-safe: muug.ca
* 2025-01-12 04:26:28 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 04:26:28 (9251) [INFO] Trying other mirror.
* 2025-01-12 04:26:28 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-12 04:26:28 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-12 04:26:28 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-12 04:26:28 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-12 04:26:28 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-12 04:26:28 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-12 04:26:28 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-12 04:26:28 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-12 04:26:28 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-12 04:26:28 (9251) [INFO]         or
* 2025-01-12 04:26:28 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-12 04:26:28 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-12 04:26:28 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-12 04:26:28 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-12 04:26:28 (9251) [INFO]         compromise:
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-12 04:26:28 (9251) [INFO] 
* 2025-01-12 04:26:28 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-12 04:26:28 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 04:26:28 (9268) [INFO] 
* 2025-01-12 04:26:28 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 04:26:28 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-12 04:26:28 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-12 04:26:28 (9238) [INFO] 
* 2025-01-12 04:26:29 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 04:26:29 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-12 04:26:29 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-12 04:26:29 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-12 04:26:29 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-12 04:26:29 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-12 04:26:29 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-12 04:26:29 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-12 04:26:29 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-12 04:26:29 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-12 04:26:29 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-12 04:26:29 (9268) [INFO] 
* 2025-01-12 04:26:29 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-12 04:26:29 (9238) [INFO] 
* 2025-01-12 04:26:29 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 04:26:29 (9251) [INFO] Determining fastest mirrors
* 2025-01-12 04:26:32 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-12 04:26:32 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-12 04:26:32 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-12 04:26:32 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-12 04:26:32 (9251) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-12 04:26:33 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 04:26:33 (9251) [INFO] Trying other mirror.
* 2025-01-12 04:26:33 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-12 04:26:33 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-12 04:26:33 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-12 04:26:33 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-12 04:26:33 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-12 04:26:33 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-12 04:26:33 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-12 04:26:33 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-12 04:26:33 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-12 04:26:33 (9251) [INFO]         or
* 2025-01-12 04:26:33 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-12 04:26:33 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-12 04:26:33 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-12 04:26:33 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-12 04:26:33 (9251) [INFO]         compromise:
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-12 04:26:33 (9251) [INFO] 
* 2025-01-12 04:26:33 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-12 04:26:33 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 04:26:33 (9268) [INFO] 
* 2025-01-12 04:26:33 (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 04:26:33 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 04:26:33 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-12 04:26:34 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eJzCY3A9jJ/ea_profile.json
* 2025-01-12 04:26:35 (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/eJzCY3A9jJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-12 04:26:35 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-13 04:25:42 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-13 04:25:42 (10313) [INFO] Script is up to date.
* 2025-01-13 04:25:43 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-13 04:25:43 (9238) [INFO] 
* 2025-01-13 04:25:46 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-13 04:25:46 (9238) [INFO] 
* 2025-01-13 04:25:53 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-13 04:25:53 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-13 04:25:53 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-13 04:25:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-13 04:25:53 (9238) [INFO] 
* 2025-01-13 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 04:25:54 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-13 04:25:54 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-13 04:25:54 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-13 04:25:54 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-13 04:25:54 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-13 04:25:54 (9251) [INFO]  * remi-safe: muug.ca
* 2025-01-13 04:25:55 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 04:25:55 (9251) [INFO] Trying other mirror.
* 2025-01-13 04:25:55 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-13 04:25:55 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-13 04:25:55 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-13 04:25:55 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-13 04:25:55 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-13 04:25:55 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-13 04:25:55 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-13 04:25:55 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-13 04:25:55 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-13 04:25:55 (9251) [INFO]         or
* 2025-01-13 04:25:55 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-13 04:25:55 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-13 04:25:55 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-13 04:25:55 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-13 04:25:55 (9251) [INFO]         compromise:
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-13 04:25:55 (9251) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-13 04:25:55 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 04:25:55 (9268) [INFO] 
* 2025-01-13 04:25:55 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 04:25:55 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-13 04:25:55 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-13 04:25:55 (9238) [INFO] 
* 2025-01-13 04:25:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 04:25:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-13 04:25:55 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-13 04:25:55 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-13 04:25:55 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-13 04:25:55 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-13 04:25:55 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-13 04:25:55 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-13 04:25:55 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-13 04:25:55 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-13 04:25:55 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-13 04:25:55 (9268) [INFO] 
* 2025-01-13 04:25:55 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-13 04:25:55 (9238) [INFO] 
* 2025-01-13 04:25:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 04:25:56 (9251) [INFO] Determining fastest mirrors
* 2025-01-13 04:25:59 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-13 04:25:59 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-13 04:25:59 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-13 04:25:59 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-13 04:25:59 (9251) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-13 04:26:00 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 04:26:00 (9251) [INFO] Trying other mirror.
* 2025-01-13 04:26:00 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-13 04:26:00 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-13 04:26:00 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-13 04:26:00 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-13 04:26:00 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-13 04:26:00 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-13 04:26:00 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-13 04:26:00 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-13 04:26:00 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-13 04:26:00 (9251) [INFO]         or
* 2025-01-13 04:26:00 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-13 04:26:00 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-13 04:26:00 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-13 04:26:00 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-13 04:26:00 (9251) [INFO]         compromise:
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-13 04:26:00 (9251) [INFO] 
* 2025-01-13 04:26:00 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-13 04:26:00 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 04:26:00 (9268) [INFO] 
* 2025-01-13 04:26:00 (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 04:26:00 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 04:26:00 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-13 04:26:01 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6V3o_FLLYT/ea_profile.json
* 2025-01-13 04:26:03 (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/6V3o_FLLYT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-13 04:26:03 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-14 04:25:34 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-14 04:25:35 (10313) [INFO] Script is up to date.
* 2025-01-14 04:25:36 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-14 04:25:36 (9238) [INFO] 
* 2025-01-14 04:25:39 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-14 04:25:39 (9238) [INFO] 
* 2025-01-14 04:25:46 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-14 04:25:46 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-14 04:25:46 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-14 04:25:46 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-14 04:25:46 (9238) [INFO] 
* 2025-01-14 04:25:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 04:25:46 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-14 04:25:47 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-14 04:25:47 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-14 04:25:47 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-14 04:25:47 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-14 04:25:47 (9251) [INFO]  * remi-safe: muug.ca
* 2025-01-14 04:25:48 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 04:25:48 (9251) [INFO] Trying other mirror.
* 2025-01-14 04:25:48 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-14 04:25:48 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-14 04:25:48 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-14 04:25:48 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-14 04:25:48 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-14 04:25:48 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-14 04:25:48 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-14 04:25:48 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-14 04:25:48 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-14 04:25:48 (9251) [INFO]         or
* 2025-01-14 04:25:48 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-14 04:25:48 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-14 04:25:48 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-14 04:25:48 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-14 04:25:48 (9251) [INFO]         compromise:
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-14 04:25:48 (9251) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-14 04:25:48 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 04:25:48 (9268) [INFO] 
* 2025-01-14 04:25:48 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 04:25:48 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-14 04:25:48 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-14 04:25:48 (9238) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 04:25:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-14 04:25:48 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-14 04:25:48 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-14 04:25:48 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-14 04:25:48 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-14 04:25:48 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-14 04:25:48 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-14 04:25:48 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-14 04:25:48 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-14 04:25:48 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-14 04:25:48 (9268) [INFO] 
* 2025-01-14 04:25:48 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-14 04:25:48 (9238) [INFO] 
* 2025-01-14 04:25:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 04:25:48 (9251) [INFO] Determining fastest mirrors
* 2025-01-14 04:25:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-14 04:25:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-14 04:25:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-14 04:25:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-14 04:25:53 (9251) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-14 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 04:25:53 (9251) [INFO] Trying other mirror.
* 2025-01-14 04:25:53 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-14 04:25:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-14 04:25:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-14 04:25:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-14 04:25:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-14 04:25:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-14 04:25:53 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-14 04:25:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-14 04:25:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-14 04:25:53 (9251) [INFO]         or
* 2025-01-14 04:25:53 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-14 04:25:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-14 04:25:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-14 04:25:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-14 04:25:53 (9251) [INFO]         compromise:
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-14 04:25:53 (9251) [INFO] 
* 2025-01-14 04:25:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-14 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 04:25:53 (9268) [INFO] 
* 2025-01-14 04:25: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-14 04:25:53 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 04:25:53 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-14 04:25:54 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ut_nfl8s2R/ea_profile.json
* 2025-01-14 04:25: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/ut_nfl8s2R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-14 04:25:56 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-15 04:25:40 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-15 04:25:40 (10313) [INFO] Script is up to date.
* 2025-01-15 04:25:41 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-15 04:25:41 (9238) [INFO] 
* 2025-01-15 04:25:44 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-15 04:25:44 (9238) [INFO] 
* 2025-01-15 04:25:50 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-15 04:25:50 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-15 04:25:50 (5934) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-15 04:25:50 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-15 04:25:50 (9238) [INFO] 
* 2025-01-15 04:25:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 04:25:50 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-15 04:25:52 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-15 04:25:52 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-15 04:25:52 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-15 04:25:52 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-15 04:25:52 (9251) [INFO]  * remi-safe: muug.ca
* 2025-01-15 04:25:52 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 04:25:52 (9251) [INFO] Trying other mirror.
* 2025-01-15 04:25:52 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-15 04:25:52 (9251) [INFO] 
* 2025-01-15 04:25:52 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-15 04:25:52 (9251) [INFO] 
* 2025-01-15 04:25:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-15 04:25:52 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-15 04:25:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-15 04:25:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-15 04:25:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-15 04:25:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-15 04:25:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-15 04:25:53 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-15 04:25:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-15 04:25:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-15 04:25:53 (9251) [INFO]         or
* 2025-01-15 04:25:53 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-15 04:25:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-15 04:25:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-15 04:25:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-15 04:25:53 (9251) [INFO]         compromise:
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-15 04:25:53 (9251) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-15 04:25:53 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 04:25:53 (9268) [INFO] 
* 2025-01-15 04:25:53 (5793) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 04:25:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-15 04:25:53 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-15 04:25:53 (9238) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 04:25:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-15 04:25:53 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-15 04:25:53 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-15 04:25:53 (9251) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-15 04:25:53 (9251) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-15 04:25:53 (9251) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-15 04:25:53 (9251) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-15 04:25:53 (9251) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-15 04:25:53 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-15 04:25:53 (9251) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-15 04:25:53 (9268) [INFO] 
* 2025-01-15 04:25:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-15 04:25:53 (9238) [INFO] 
* 2025-01-15 04:25:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 04:25:53 (9251) [INFO] Determining fastest mirrors
* 2025-01-15 04:25:57 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-15 04:25:57 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-15 04:25:57 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-15 04:25:57 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-15 04:25:57 (9251) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-15 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 04:25:58 (9251) [INFO] Trying other mirror.
* 2025-01-15 04:25:58 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-15 04:25:58 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-15 04:25:58 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-15 04:25:58 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-15 04:25:58 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-15 04:25:58 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-15 04:25:58 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-15 04:25:58 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-15 04:25:58 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-15 04:25:58 (9251) [INFO]         or
* 2025-01-15 04:25:58 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-15 04:25:58 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-15 04:25:58 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-15 04:25:58 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-15 04:25:58 (9251) [INFO]         compromise:
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-15 04:25:58 (9251) [INFO] 
* 2025-01-15 04:25:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-15 04:25:58 (9251) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 04:25:58 (9268) [INFO] 
* 2025-01-15 04:25:58 (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 04:25:58 (5804) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 04:25:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-15 04:25:59 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8w0qxdDL88/ea_profile.json
* 2025-01-15 04:26: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/8w0qxdDL88/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-15 04:26:01 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-16 04:26:27 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-16 04:26:27 (10296) [INFO] Newer version of script found. Downloading.
* 2025-01-16 04:26:28 (10305) [INFO] Script update to version 60 successful.
* 2025-01-16 04:26:31 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-16 04:26:31 (9401) [INFO] 
* 2025-01-16 04:26:34 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-16 04:26:34 (9401) [INFO] 
* 2025-01-16 04:26:42 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-16 04:26:42 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-16 04:26:42 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-16 04:26:42 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-16 04:26:42 (9401) [INFO] 
* 2025-01-16 04:26:42 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-16 04:26:42 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-16 04:26:44 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-16 04:26:44 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-16 04:26:44 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-16 04:26:44 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-16 04:26:44 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-16 04:26:45 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-16 04:26:45 (9414) [INFO] Trying other mirror.
* 2025-01-16 04:26:45 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-16 04:26:45 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-16 04:26:45 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-16 04:26:45 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-16 04:26:45 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-16 04:26:45 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-16 04:26:45 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-16 04:26:45 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-16 04:26:45 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-16 04:26:45 (9414) [INFO]         or
* 2025-01-16 04:26:45 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-16 04:26:45 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-16 04:26:45 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-16 04:26:45 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-16 04:26:45 (9414) [INFO]         compromise:
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-16 04:26:45 (9414) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-16 04:26:45 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-16 04:26:45 (9431) [INFO] 
* 2025-01-16 04:26:45 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-16 04:26:45 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-16 04:26:45 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-16 04:26:45 (9401) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-16 04:26:45 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-16 04:26:45 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-16 04:26:45 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-16 04:26:45 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-16 04:26:45 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-16 04:26:45 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-16 04:26:45 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-16 04:26:45 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-16 04:26:45 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-16 04:26:45 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-16 04:26:45 (9431) [INFO] 
* 2025-01-16 04:26:45 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-16 04:26:45 (9401) [INFO] 
* 2025-01-16 04:26:45 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-16 04:26:46 (9414) [INFO] Determining fastest mirrors
* 2025-01-16 04:26:51 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-16 04:26:51 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-16 04:26:51 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-16 04:26:51 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-16 04:26:51 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-16 04:26:52 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-16 04:26:52 (9414) [INFO] Trying other mirror.
* 2025-01-16 04:26:52 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-16 04:26:52 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-16 04:26:52 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-16 04:26:52 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-16 04:26:52 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-16 04:26:52 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-16 04:26:52 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-16 04:26:52 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-16 04:26:52 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-16 04:26:52 (9414) [INFO]         or
* 2025-01-16 04:26:52 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-16 04:26:52 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-16 04:26:52 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-16 04:26:52 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-16 04:26:52 (9414) [INFO]         compromise:
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-16 04:26:52 (9414) [INFO] 
* 2025-01-16 04:26:52 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-16 04:26:52 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-16 04:26:52 (9431) [INFO] 
* 2025-01-16 04:26: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-01-16 04:26:52 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-16 04:26:52 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-16 04:26:53 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qz8Phob1Wx/ea_profile.json
* 2025-01-16 04:26: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/qz8Phob1Wx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-16 04:26:56 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-17 04:25:40 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-17 04:25:40 (10480) [INFO] Script is up to date.
* 2025-01-17 04:25:41 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-17 04:25:41 (9401) [INFO] 
* 2025-01-17 04:25:45 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-17 04:25:45 (9401) [INFO] 
* 2025-01-17 04:25:52 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-17 04:25:52 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-17 04:25:52 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-17 04:25:52 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-17 04:25:52 (9401) [INFO] 
* 2025-01-17 04:25:53 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-17 04:25:53 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-17 04:25:53 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-17 04:25:53 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-17 04:25:53 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-17 04:25:53 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-17 04:25:53 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-17 04:25:54 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-17 04:25:54 (9414) [INFO] Trying other mirror.
* 2025-01-17 04:25:54 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-17 04:25:54 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-17 04:25:54 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-17 04:25:54 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-17 04:25:54 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-17 04:25:54 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-17 04:25:54 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-17 04:25:54 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-17 04:25:54 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-17 04:25:54 (9414) [INFO]         or
* 2025-01-17 04:25:54 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-17 04:25:54 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-17 04:25:54 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-17 04:25:54 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-17 04:25:54 (9414) [INFO]         compromise:
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-17 04:25:54 (9414) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-17 04:25:54 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-17 04:25:54 (9431) [INFO] 
* 2025-01-17 04:25:54 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-17 04:25:54 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-17 04:25:54 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-17 04:25:54 (9401) [INFO] 
* 2025-01-17 04:25:54 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-17 04:25:54 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-17 04:25:54 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-17 04:25:54 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-17 04:25:54 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-17 04:25:54 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-17 04:25:54 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-17 04:25:54 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-17 04:25:54 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-17 04:25:54 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-17 04:25:54 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-17 04:25:54 (9431) [INFO] 
* 2025-01-17 04:25:54 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-17 04:25:54 (9401) [INFO] 
* 2025-01-17 04:25:55 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-17 04:25:55 (9414) [INFO] Determining fastest mirrors
* 2025-01-17 04:25:58 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-17 04:25:58 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-17 04:25:58 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-17 04:25:58 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-17 04:25:58 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-17 04:25:58 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-17 04:25:58 (9414) [INFO] Trying other mirror.
* 2025-01-17 04:25:58 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-17 04:25:58 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-17 04:25:58 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-17 04:25:58 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-17 04:25:58 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-17 04:25:58 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-17 04:25:58 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-17 04:25:58 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-17 04:25:58 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-17 04:25:58 (9414) [INFO]         or
* 2025-01-17 04:25:58 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-17 04:25:58 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-17 04:25:58 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-17 04:25:58 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-17 04:25:58 (9414) [INFO]         compromise:
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-17 04:25:58 (9414) [INFO] 
* 2025-01-17 04:25:58 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-17 04:25:58 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-17 04:25:58 (9431) [INFO] 
* 2025-01-17 04:25:58 (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-01-17 04:25:58 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-17 04:25:59 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-17 04:25:59 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jfIr1NpL6n/ea_profile.json
* 2025-01-17 04:26:01 (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/jfIr1NpL6n/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-17 04:26:01 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-18 04:26:35 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-18 04:26:35 (10480) [INFO] Script is up to date.
* 2025-01-18 04:26:37 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-18 04:26:37 (9401) [INFO] 
* 2025-01-18 04:26:40 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-18 04:26:40 (9401) [INFO] 
* 2025-01-18 04:26:47 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-18 04:26:47 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-18 04:26:47 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-18 04:26:47 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-18 04:26:47 (9401) [INFO] 
* 2025-01-18 04:26:48 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-18 04:26:48 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-18 04:26:49 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-18 04:26:49 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-18 04:26:49 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-18 04:26:49 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-18 04:26:49 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-18 04:26:50 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-18 04:26:50 (9414) [INFO] Trying other mirror.
* 2025-01-18 04:26:50 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-18 04:26:50 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-18 04:26:50 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-18 04:26:50 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-18 04:26:50 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-18 04:26:50 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-18 04:26:50 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-18 04:26:50 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-18 04:26:50 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-18 04:26:50 (9414) [INFO]         or
* 2025-01-18 04:26:50 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-18 04:26:50 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-18 04:26:50 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-18 04:26:50 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-18 04:26:50 (9414) [INFO]         compromise:
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-18 04:26:50 (9414) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-18 04:26:50 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-18 04:26:50 (9431) [INFO] 
* 2025-01-18 04:26:50 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-18 04:26:50 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-18 04:26:50 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-18 04:26:50 (9401) [INFO] 
* 2025-01-18 04:26:50 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-18 04:26:50 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-18 04:26:50 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-18 04:26:50 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-18 04:26:50 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-18 04:26:50 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-18 04:26:50 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-18 04:26:50 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-18 04:26:50 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-18 04:26:50 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-18 04:26:50 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-18 04:26:50 (9431) [INFO] 
* 2025-01-18 04:26:50 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-18 04:26:50 (9401) [INFO] 
* 2025-01-18 04:26:51 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-18 04:26:51 (9414) [INFO] Determining fastest mirrors
* 2025-01-18 04:26:55 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-18 04:26:55 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-18 04:26:55 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-18 04:26:55 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-18 04:26:55 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-18 04:26:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-18 04:26:55 (9414) [INFO] Trying other mirror.
* 2025-01-18 04:26:55 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-18 04:26:55 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-18 04:26:55 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-18 04:26:55 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-18 04:26:55 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-18 04:26:55 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-18 04:26:55 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-18 04:26:55 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-18 04:26:55 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-18 04:26:55 (9414) [INFO]         or
* 2025-01-18 04:26:55 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-18 04:26:55 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-18 04:26:55 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-18 04:26:55 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-18 04:26:55 (9414) [INFO]         compromise:
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-18 04:26:55 (9414) [INFO] 
* 2025-01-18 04:26:55 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-18 04:26:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-18 04:26:55 (9431) [INFO] 
* 2025-01-18 04:26:55 (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-01-18 04:26:55 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-18 04:26:55 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-18 04:26:56 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pY0xH5xbm6/ea_profile.json
* 2025-01-18 04:26:59 (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/pY0xH5xbm6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-18 04:26:59 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-19 04:26:31 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-19 04:26:31 (10480) [INFO] Script is up to date.
* 2025-01-19 04:26:32 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-19 04:26:32 (9401) [INFO] 
* 2025-01-19 04:26:35 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-19 04:26:35 (9401) [INFO] 
* 2025-01-19 04:26:42 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-19 04:26:42 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-19 04:26:42 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-19 04:26:42 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-19 04:26:42 (9401) [INFO] 
* 2025-01-19 04:26:42 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-19 04:26:43 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-19 04:26:43 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-19 04:26:43 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-19 04:26:43 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-19 04:26:43 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-19 04:26:43 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-19 04:26:44 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-19 04:26:44 (9414) [INFO] Trying other mirror.
* 2025-01-19 04:26:44 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-19 04:26:44 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-19 04:26:44 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-19 04:26:44 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-19 04:26:44 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-19 04:26:44 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-19 04:26:44 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-19 04:26:44 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-19 04:26:44 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-19 04:26:44 (9414) [INFO]         or
* 2025-01-19 04:26:44 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-19 04:26:44 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-19 04:26:44 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-19 04:26:44 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-19 04:26:44 (9414) [INFO]         compromise:
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-19 04:26:44 (9414) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-19 04:26:44 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-19 04:26:44 (9431) [INFO] 
* 2025-01-19 04:26:44 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-19 04:26:44 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-19 04:26:44 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-19 04:26:44 (9401) [INFO] 
* 2025-01-19 04:26:44 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-19 04:26:44 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-19 04:26:44 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-19 04:26:44 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-19 04:26:44 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-19 04:26:44 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-19 04:26:44 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-19 04:26:44 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-19 04:26:44 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-19 04:26:44 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-19 04:26:44 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-19 04:26:44 (9431) [INFO] 
* 2025-01-19 04:26:44 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-19 04:26:44 (9401) [INFO] 
* 2025-01-19 04:26:45 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-19 04:26:45 (9414) [INFO] Determining fastest mirrors
* 2025-01-19 04:26:48 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-19 04:26:48 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-19 04:26:48 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-19 04:26:48 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-19 04:26:48 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-19 04:26:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-19 04:26:48 (9414) [INFO] Trying other mirror.
* 2025-01-19 04:26:48 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-19 04:26:48 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-19 04:26:48 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-19 04:26:48 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-19 04:26:48 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-19 04:26:48 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-19 04:26:48 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-19 04:26:48 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-19 04:26:48 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-19 04:26:48 (9414) [INFO]         or
* 2025-01-19 04:26:48 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-19 04:26:48 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-19 04:26:48 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-19 04:26:48 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-19 04:26:48 (9414) [INFO]         compromise:
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-19 04:26:48 (9414) [INFO] 
* 2025-01-19 04:26:48 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-19 04:26:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-19 04:26:48 (9431) [INFO] 
* 2025-01-19 04:26:48 (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-01-19 04:26:48 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-19 04:26:49 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-19 04:26:49 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gONuYA1eZY/ea_profile.json
* 2025-01-19 04:26:51 (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/gONuYA1eZY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-19 04:26:51 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-20 04:25:34 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-20 04:25:35 (10480) [INFO] Script is up to date.
* 2025-01-20 04:25:36 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-20 04:25:36 (9401) [INFO] 
* 2025-01-20 04:25:39 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-20 04:25:39 (9401) [INFO] 
* 2025-01-20 04:25:44 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-20 04:25:44 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-20 04:25:44 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-20 04:25:45 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-20 04:25:45 (9401) [INFO] 
* 2025-01-20 04:25:45 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-20 04:25:45 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-20 04:25:46 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-20 04:25:46 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-20 04:25:46 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-20 04:25:46 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-20 04:25:46 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-20 04:25:46 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-20 04:25:46 (9414) [INFO] Trying other mirror.
* 2025-01-20 04:25:46 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-20 04:25:46 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-20 04:25:46 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-20 04:25:46 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-20 04:25:46 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-20 04:25:46 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-20 04:25:46 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-20 04:25:46 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-20 04:25:46 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-20 04:25:46 (9414) [INFO]         or
* 2025-01-20 04:25:46 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-20 04:25:46 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-20 04:25:46 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-20 04:25:46 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-20 04:25:46 (9414) [INFO]         compromise:
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-20 04:25:46 (9414) [INFO] 
* 2025-01-20 04:25:46 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-20 04:25:46 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-20 04:25:46 (9431) [INFO] 
* 2025-01-20 04:25:46 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-20 04:25:46 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-20 04:25:46 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-20 04:25:46 (9401) [INFO] 
* 2025-01-20 04:25:47 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-20 04:25:47 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-20 04:25:47 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-20 04:25:47 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-20 04:25:47 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-20 04:25:47 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-20 04:25:47 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-20 04:25:47 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-20 04:25:47 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-20 04:25:47 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-20 04:25:47 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-20 04:25:47 (9431) [INFO] 
* 2025-01-20 04:25:47 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-20 04:25:47 (9401) [INFO] 
* 2025-01-20 04:25:47 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-20 04:25:47 (9414) [INFO] Determining fastest mirrors
* 2025-01-20 04:25:51 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-20 04:25:51 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-20 04:25:51 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-20 04:25:51 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-20 04:25:51 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-20 04:25:51 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-20 04:25:51 (9414) [INFO] Trying other mirror.
* 2025-01-20 04:25:51 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-20 04:25:51 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-20 04:25:51 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-20 04:25:51 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-20 04:25:51 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-20 04:25:51 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-20 04:25:51 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-20 04:25:51 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-20 04:25:51 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-20 04:25:51 (9414) [INFO]         or
* 2025-01-20 04:25:51 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-20 04:25:51 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-20 04:25:51 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-20 04:25:51 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-20 04:25:51 (9414) [INFO]         compromise:
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-20 04:25:51 (9414) [INFO] 
* 2025-01-20 04:25:51 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-20 04:25:51 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-20 04:25:51 (9431) [INFO] 
* 2025-01-20 04:25:51 (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-01-20 04:25:51 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-20 04:25:52 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-20 04:25:52 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZRY9HWfFqE/ea_profile.json
* 2025-01-20 04:25:54 (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/ZRY9HWfFqE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-20 04:25:54 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-21 04:25:35 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-21 04:25:35 (10480) [INFO] Script is up to date.
* 2025-01-21 04:25:36 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-21 04:25:36 (9401) [INFO] 
* 2025-01-21 04:25:39 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-21 04:25:39 (9401) [INFO] 
* 2025-01-21 04:26:01 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-21 04:26:01 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-21 04:26:01 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-21 04:26:01 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-21 04:26:01 (9401) [INFO] 
* 2025-01-21 04:26:01 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-21 04:26:01 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-21 04:26:17 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-21 04:26:17 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-21 04:26:17 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-21 04:26:17 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-21 04:26:17 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-21 04:26:17 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-21 04:26:17 (9414) [INFO] Trying other mirror.
* 2025-01-21 04:26:17 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-21 04:26:17 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-21 04:26:17 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-21 04:26:17 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-21 04:26:17 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-21 04:26:17 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-21 04:26:17 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-21 04:26:17 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-21 04:26:17 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-21 04:26:17 (9414) [INFO]         or
* 2025-01-21 04:26:17 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-21 04:26:17 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-21 04:26:17 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-21 04:26:17 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-21 04:26:17 (9414) [INFO]         compromise:
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-21 04:26:17 (9414) [INFO] 
* 2025-01-21 04:26:17 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-21 04:26:17 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-21 04:26:18 (9431) [INFO] 
* 2025-01-21 04:26:18 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-21 04:26:18 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-21 04:26:18 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-21 04:26:18 (9401) [INFO] 
* 2025-01-21 04:26:18 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-21 04:26:18 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-21 04:26:18 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-21 04:26:18 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-21 04:26:18 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-21 04:26:18 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-21 04:26:18 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-21 04:26:18 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-21 04:26:18 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-21 04:26:18 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-21 04:26:18 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-21 04:26:18 (9431) [INFO] 
* 2025-01-21 04:26:18 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-21 04:26:18 (9401) [INFO] 
* 2025-01-21 04:26:18 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-21 04:26:18 (9414) [INFO] Determining fastest mirrors
* 2025-01-21 04:26:22 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-21 04:26:22 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-21 04:26:22 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-21 04:26:22 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-21 04:26:22 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-21 04:26:23 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-21 04:26:23 (9414) [INFO] Trying other mirror.
* 2025-01-21 04:26:23 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-21 04:26:23 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-21 04:26:23 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-21 04:26:23 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-21 04:26:23 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-21 04:26:23 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-21 04:26:23 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-21 04:26:23 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-21 04:26:23 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-21 04:26:23 (9414) [INFO]         or
* 2025-01-21 04:26:23 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-21 04:26:23 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-21 04:26:23 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-21 04:26:23 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-21 04:26:23 (9414) [INFO]         compromise:
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-21 04:26:23 (9414) [INFO] 
* 2025-01-21 04:26:23 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-21 04:26:23 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-21 04:26:23 (9431) [INFO] 
* 2025-01-21 04:26:23 (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-01-21 04:26:23 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-21 04:26:23 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-21 04:26:24 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VieQbwqSnA/ea_profile.json
* 2025-01-21 04:26:26 (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/VieQbwqSnA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-21 04:26:26 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-22 04:25:40 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-22 04:25:40 (10480) [INFO] Script is up to date.
* 2025-01-22 04:25:41 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-22 04:25:41 (9401) [INFO] 
* 2025-01-22 04:25:44 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-22 04:25:44 (9401) [INFO] 
* 2025-01-22 04:25:51 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-22 04:25:51 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-22 04:25:51 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-22 04:25:51 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-22 04:25:51 (9401) [INFO] 
* 2025-01-22 04:25:51 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-22 04:25:51 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-22 04:25:52 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-22 04:25:52 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-22 04:25:52 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-22 04:25:52 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-22 04:25:52 (9414) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-22 04:25:53 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-22 04:25:53 (9414) [INFO] Trying other mirror.
* 2025-01-22 04:25:53 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-22 04:25:53 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-22 04:25:53 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-22 04:25:53 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-22 04:25:53 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-22 04:25:53 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-22 04:25:53 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-22 04:25:53 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-22 04:25:53 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-22 04:25:53 (9414) [INFO]         or
* 2025-01-22 04:25:53 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-22 04:25:53 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-22 04:25:53 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-22 04:25:53 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-22 04:25:53 (9414) [INFO]         compromise:
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-22 04:25:53 (9414) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-22 04:25:53 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-22 04:25:53 (9431) [INFO] 
* 2025-01-22 04:25:53 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-22 04:25:53 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-22 04:25:53 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-22 04:25:53 (9401) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-22 04:25:53 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-22 04:25:53 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-22 04:25:53 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-22 04:25:53 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-22 04:25:53 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-22 04:25:53 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-22 04:25:53 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-22 04:25:53 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-22 04:25:53 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-22 04:25:53 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-22 04:25:53 (9431) [INFO] 
* 2025-01-22 04:25:53 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-22 04:25:53 (9401) [INFO] 
* 2025-01-22 04:25:53 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-22 04:25:54 (9414) [INFO] Determining fastest mirrors
* 2025-01-22 04:25:56 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-22 04:25:56 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-22 04:25:56 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-22 04:25:56 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-22 04:25:56 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-22 04:25:57 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-22 04:25:57 (9414) [INFO] Trying other mirror.
* 2025-01-22 04:25:57 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-22 04:25:57 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-22 04:25:57 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-22 04:25:57 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-22 04:25:57 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-22 04:25:57 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-22 04:25:57 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-22 04:25:57 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-22 04:25:57 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-22 04:25:57 (9414) [INFO]         or
* 2025-01-22 04:25:57 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-22 04:25:57 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-22 04:25:57 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-22 04:25:57 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-22 04:25:57 (9414) [INFO]         compromise:
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-22 04:25:57 (9414) [INFO] 
* 2025-01-22 04:25:57 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-22 04:25:57 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-22 04:25:57 (9431) [INFO] 
* 2025-01-22 04:25:57 (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-01-22 04:25:57 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-22 04:25:57 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-22 04:25:58 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7Li3Lwtxir/ea_profile.json
* 2025-01-22 04:26:00 (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/7Li3Lwtxir/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-22 04:26:00 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-23 04:25:35 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-23 04:25:35 (10480) [INFO] Script is up to date.
* 2025-01-23 04:25:36 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-23 04:25:36 (9401) [INFO] 
* 2025-01-23 04:25:38 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-23 04:25:38 (9401) [INFO] 
* 2025-01-23 04:25:45 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-23 04:25:45 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-23 04:25:45 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-23 04:25:45 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-23 04:25:45 (9401) [INFO] 
* 2025-01-23 04:25:45 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-23 04:25:45 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-23 04:25:47 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-23 04:25:47 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-23 04:25:47 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-23 04:25:47 (9414) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-23 04:25:47 (9414) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-23 04:25:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-23 04:25:48 (9414) [INFO] Trying other mirror.
* 2025-01-23 04:25:48 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-23 04:25:48 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-23 04:25:48 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-23 04:25:48 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-23 04:25:48 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-23 04:25:48 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-23 04:25:48 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-23 04:25:48 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-23 04:25:48 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-23 04:25:48 (9414) [INFO]         or
* 2025-01-23 04:25:48 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-23 04:25:48 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-23 04:25:48 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-23 04:25:48 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-23 04:25:48 (9414) [INFO]         compromise:
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-23 04:25:48 (9414) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-23 04:25:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-23 04:25:48 (9431) [INFO] 
* 2025-01-23 04:25:48 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-23 04:25:48 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-23 04:25:48 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-23 04:25:48 (9401) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-23 04:25:48 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-23 04:25:48 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-23 04:25:48 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-23 04:25:48 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-23 04:25:48 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-23 04:25:48 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-23 04:25:48 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-23 04:25:48 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-23 04:25:48 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-23 04:25:48 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-23 04:25:48 (9431) [INFO] 
* 2025-01-23 04:25:48 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-23 04:25:48 (9401) [INFO] 
* 2025-01-23 04:25:48 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-23 04:25:48 (9414) [INFO] Determining fastest mirrors
* 2025-01-23 04:25:52 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-23 04:25:52 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-23 04:25:52 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-23 04:25:52 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-23 04:25:52 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-23 04:25:53 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-23 04:25:53 (9414) [INFO] Trying other mirror.
* 2025-01-23 04:25:53 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-23 04:25:53 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-23 04:25:53 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-23 04:25:53 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-23 04:25:53 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-23 04:25:53 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-23 04:25:53 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-23 04:25:53 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-23 04:25:53 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-23 04:25:53 (9414) [INFO]         or
* 2025-01-23 04:25:53 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-23 04:25:53 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-23 04:25:53 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-23 04:25:53 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-23 04:25:53 (9414) [INFO]         compromise:
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-23 04:25:53 (9414) [INFO] 
* 2025-01-23 04:25:53 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-23 04:25:53 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-23 04:25:53 (9431) [INFO] 
* 2025-01-23 04:25:53 (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-01-23 04:25:53 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-23 04:25:53 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-23 04:25:54 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Pc_RhKLPIJ/ea_profile.json
* 2025-01-23 04:25:57 (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/Pc_RhKLPIJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-23 04:25:57 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-24 04:25:35 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-24 04:25:35 (10480) [INFO] Script is up to date.
* 2025-01-24 04:25:36 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-24 04:25:36 (9401) [INFO] 
* 2025-01-24 04:25:40 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-24 04:25:40 (9401) [INFO] 
* 2025-01-24 04:25:46 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-24 04:25:46 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-24 04:25:46 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-24 04:25:46 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-24 04:25:46 (9401) [INFO] 
* 2025-01-24 04:25:46 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-24 04:25:47 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-24 04:25:48 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-24 04:25:48 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-24 04:25:48 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-24 04:25:48 (9414) [INFO]  * epel: dl.fedoraproject.org
* 2025-01-24 04:25:48 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-24 04:25:49 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-24 04:25:49 (9414) [INFO] Trying other mirror.
* 2025-01-24 04:25:49 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-24 04:25:49 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-24 04:25:49 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-24 04:25:49 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-24 04:25:49 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-24 04:25:49 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-24 04:25:49 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-24 04:25:49 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-24 04:25:49 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-24 04:25:49 (9414) [INFO]         or
* 2025-01-24 04:25:49 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-24 04:25:49 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-24 04:25:49 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-24 04:25:49 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-24 04:25:49 (9414) [INFO]         compromise:
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-24 04:25:49 (9414) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-24 04:25:49 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-24 04:25:49 (9431) [INFO] 
* 2025-01-24 04:25:49 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-24 04:25:49 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-24 04:25:49 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-24 04:25:49 (9401) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-24 04:25:49 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-24 04:25:49 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-24 04:25:49 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-24 04:25:49 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-24 04:25:49 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-24 04:25:49 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-24 04:25:49 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-24 04:25:49 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-24 04:25:49 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-24 04:25:49 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-24 04:25:49 (9431) [INFO] 
* 2025-01-24 04:25:49 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-24 04:25:49 (9401) [INFO] 
* 2025-01-24 04:25:49 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-24 04:25:49 (9414) [INFO] Determining fastest mirrors
* 2025-01-24 04:25:53 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-24 04:25:53 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-24 04:25:53 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-24 04:25:53 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-24 04:25:53 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-24 04:25:54 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-24 04:25:54 (9414) [INFO] Trying other mirror.
* 2025-01-24 04:25:54 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-24 04:25:54 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-24 04:25:54 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-24 04:25:54 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-24 04:25:54 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-24 04:25:54 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-24 04:25:54 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-24 04:25:54 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-24 04:25:54 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-24 04:25:54 (9414) [INFO]         or
* 2025-01-24 04:25:54 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-24 04:25:54 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-24 04:25:54 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-24 04:25:54 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-24 04:25:54 (9414) [INFO]         compromise:
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-24 04:25:54 (9414) [INFO] 
* 2025-01-24 04:25:54 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-24 04:25:54 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-24 04:25:54 (9431) [INFO] 
* 2025-01-24 04:25:54 (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-01-24 04:25:54 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-24 04:25:54 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-24 04:25:55 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HSdmUZ0GzW/ea_profile.json
* 2025-01-24 04:25:57 (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/HSdmUZ0GzW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-24 04:25:57 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-25 04:26:31 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-25 04:26:31 (10480) [INFO] Script is up to date.
* 2025-01-25 04:26:32 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-25 04:26:32 (9401) [INFO] 
* 2025-01-25 04:26:36 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-25 04:26:36 (9401) [INFO] 
* 2025-01-25 04:26:43 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-25 04:26:43 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-25 04:26:43 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-25 04:26:43 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-25 04:26:43 (9401) [INFO] 
* 2025-01-25 04:26:43 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-25 04:26:44 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-25 04:26:45 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-25 04:26:45 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-25 04:26:45 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-25 04:26:45 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-25 04:26:45 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-25 04:26:45 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-25 04:26:45 (9414) [INFO] Trying other mirror.
* 2025-01-25 04:26:45 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-25 04:26:45 (9414) [INFO] 
* 2025-01-25 04:26:45 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-25 04:26:45 (9414) [INFO] 
* 2025-01-25 04:26:45 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-25 04:26:45 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-25 04:26:46 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-25 04:26:46 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-25 04:26:46 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-25 04:26:46 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-25 04:26:46 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-25 04:26:46 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-25 04:26:46 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-25 04:26:46 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-25 04:26:46 (9414) [INFO]         or
* 2025-01-25 04:26:46 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-25 04:26:46 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-25 04:26:46 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-25 04:26:46 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-25 04:26:46 (9414) [INFO]         compromise:
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-25 04:26:46 (9414) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-25 04:26:46 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-25 04:26:46 (9431) [INFO] 
* 2025-01-25 04:26:46 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-25 04:26:46 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-25 04:26:46 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-25 04:26:46 (9401) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-25 04:26:46 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-25 04:26:46 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-25 04:26:46 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-25 04:26:46 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-25 04:26:46 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-25 04:26:46 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-25 04:26:46 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-25 04:26:46 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-25 04:26:46 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-25 04:26:46 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-25 04:26:46 (9431) [INFO] 
* 2025-01-25 04:26:46 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-25 04:26:46 (9401) [INFO] 
* 2025-01-25 04:26:46 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-25 04:26:46 (9414) [INFO] Determining fastest mirrors
* 2025-01-25 04:26:51 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-25 04:26:51 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-25 04:26:51 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-25 04:26:51 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-25 04:26:51 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-25 04:26:51 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-25 04:26:51 (9414) [INFO] Trying other mirror.
* 2025-01-25 04:26:51 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-25 04:26:51 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-25 04:26:51 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-25 04:26:51 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-25 04:26:51 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-25 04:26:51 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-25 04:26:51 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-25 04:26:51 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-25 04:26:51 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-25 04:26:51 (9414) [INFO]         or
* 2025-01-25 04:26:51 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-25 04:26:51 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-25 04:26:51 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-25 04:26:51 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-25 04:26:51 (9414) [INFO]         compromise:
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-25 04:26:51 (9414) [INFO] 
* 2025-01-25 04:26:51 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-25 04:26:51 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-25 04:26:51 (9431) [INFO] 
* 2025-01-25 04:26:51 (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-01-25 04:26:51 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-25 04:26:52 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-25 04:26:52 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5Q8XoaLLXF/ea_profile.json
* 2025-01-25 04:26:54 (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/5Q8XoaLLXF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-25 04:26:54 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-26 04:26:23 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-26 04:26:23 (10480) [INFO] Script is up to date.
* 2025-01-26 04:26:25 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-26 04:26:25 (9401) [INFO] 
* 2025-01-26 04:26:27 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-26 04:26:27 (9401) [INFO] 
* 2025-01-26 04:26:36 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-26 04:26:36 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-26 04:26:36 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-26 04:26:36 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-26 04:26:36 (9401) [INFO] 
* 2025-01-26 04:26:37 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-26 04:26:37 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-26 04:26:37 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-26 04:26:37 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-26 04:26:37 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-26 04:26:37 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-26 04:26:37 (9414) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-26 04:26:38 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-26 04:26:38 (9414) [INFO] Trying other mirror.
* 2025-01-26 04:26:38 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-26 04:26:38 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-26 04:26:38 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-26 04:26:38 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-26 04:26:38 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-26 04:26:38 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-26 04:26:38 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-26 04:26:38 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-26 04:26:38 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-26 04:26:38 (9414) [INFO]         or
* 2025-01-26 04:26:38 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-26 04:26:38 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-26 04:26:38 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-26 04:26:38 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-26 04:26:38 (9414) [INFO]         compromise:
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-26 04:26:38 (9414) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-26 04:26:38 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-26 04:26:38 (9431) [INFO] 
* 2025-01-26 04:26:38 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-26 04:26:38 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-26 04:26:38 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-26 04:26:38 (9401) [INFO] 
* 2025-01-26 04:26:38 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-26 04:26:38 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-26 04:26:38 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-26 04:26:38 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-26 04:26:38 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-26 04:26:38 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-26 04:26:38 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-26 04:26:38 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-26 04:26:38 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-26 04:26:38 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-26 04:26:38 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-26 04:26:39 (9431) [INFO] 
* 2025-01-26 04:26:39 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-26 04:26:39 (9401) [INFO] 
* 2025-01-26 04:26:39 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-26 04:26:39 (9414) [INFO] Determining fastest mirrors
* 2025-01-26 04:26:44 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-26 04:26:44 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-26 04:26:44 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-26 04:26:44 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-26 04:26:44 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-26 04:26:44 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-26 04:26:44 (9414) [INFO] Trying other mirror.
* 2025-01-26 04:26:44 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-26 04:26:44 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-26 04:26:44 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-26 04:26:44 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-26 04:26:44 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-26 04:26:44 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-26 04:26:44 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-26 04:26:44 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-26 04:26:44 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-26 04:26:44 (9414) [INFO]         or
* 2025-01-26 04:26:44 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-26 04:26:44 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-26 04:26:44 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-26 04:26:44 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-26 04:26:44 (9414) [INFO]         compromise:
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-26 04:26:44 (9414) [INFO] 
* 2025-01-26 04:26:44 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-26 04:26:44 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-26 04:26:44 (9431) [INFO] 
* 2025-01-26 04:26:44 (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-01-26 04:26:44 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-26 04:26:44 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-26 04:26:45 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B8tINZXLTP/ea_profile.json
* 2025-01-26 04:26:47 (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/B8tINZXLTP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-26 04:26:47 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-27 04:25:45 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-27 04:25:45 (10480) [INFO] Script is up to date.
* 2025-01-27 04:25:46 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-27 04:25:46 (9401) [INFO] 
* 2025-01-27 04:25:50 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-27 04:25:50 (9401) [INFO] 
* 2025-01-27 04:25:56 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-27 04:25:56 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-27 04:25:56 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-27 04:25:56 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-27 04:25:56 (9401) [INFO] 
* 2025-01-27 04:25:56 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-27 04:25:57 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-27 04:25:58 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-27 04:25:58 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-27 04:25:58 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-27 04:25:58 (9414) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-27 04:25:58 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-27 04:25:59 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-27 04:25:59 (9414) [INFO] Trying other mirror.
* 2025-01-27 04:25:59 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-27 04:25:59 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-27 04:25:59 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-27 04:25:59 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-27 04:25:59 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-27 04:25:59 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-27 04:25:59 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-27 04:25:59 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-27 04:25:59 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-27 04:25:59 (9414) [INFO]         or
* 2025-01-27 04:25:59 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-27 04:25:59 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-27 04:25:59 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-27 04:25:59 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-27 04:25:59 (9414) [INFO]         compromise:
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-27 04:25:59 (9414) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-27 04:25:59 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-27 04:25:59 (9431) [INFO] 
* 2025-01-27 04:25:59 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-27 04:25:59 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-27 04:25:59 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-27 04:25:59 (9401) [INFO] 
* 2025-01-27 04:25:59 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-27 04:25:59 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-27 04:25:59 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-27 04:25:59 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-27 04:25:59 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-27 04:25:59 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-27 04:25:59 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-27 04:25:59 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-27 04:25:59 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-27 04:25:59 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-27 04:25:59 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-27 04:25:59 (9431) [INFO] 
* 2025-01-27 04:25:59 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-27 04:25:59 (9401) [INFO] 
* 2025-01-27 04:26:00 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-27 04:26:00 (9414) [INFO] Determining fastest mirrors
* 2025-01-27 04:26:04 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-27 04:26:04 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-27 04:26:04 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-27 04:26:04 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-27 04:26:04 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-27 04:26:04 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-27 04:26:04 (9414) [INFO] Trying other mirror.
* 2025-01-27 04:26:04 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-27 04:26:04 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-27 04:26:04 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-27 04:26:04 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-27 04:26:04 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-27 04:26:04 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-27 04:26:04 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-27 04:26:04 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-27 04:26:04 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-27 04:26:04 (9414) [INFO]         or
* 2025-01-27 04:26:04 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-27 04:26:04 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-27 04:26:04 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-27 04:26:04 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-27 04:26:04 (9414) [INFO]         compromise:
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-27 04:26:04 (9414) [INFO] 
* 2025-01-27 04:26:04 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-27 04:26:04 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-27 04:26:04 (9431) [INFO] 
* 2025-01-27 04:26:04 (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-01-27 04:26:04 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-27 04:26:05 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-27 04:26:05 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_EdiYo8SOs/ea_profile.json
* 2025-01-27 04:26:08 (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/_EdiYo8SOs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-27 04:26:08 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-28 04:25:37 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-28 04:25:37 (10480) [INFO] Script is up to date.
* 2025-01-28 04:25:38 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-28 04:25:38 (9401) [INFO] 
* 2025-01-28 04:25:40 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-28 04:25:40 (9401) [INFO] 
* 2025-01-28 04:25:47 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-28 04:25:47 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-28 04:25:47 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-28 04:25:47 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-28 04:25:47 (9401) [INFO] 
* 2025-01-28 04:25:47 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-28 04:25:47 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-28 04:25:49 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-28 04:25:49 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-28 04:25:49 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-28 04:25:49 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-28 04:25:49 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-28 04:25:50 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-28 04:25:50 (9414) [INFO] Trying other mirror.
* 2025-01-28 04:25:50 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-28 04:25:50 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-28 04:25:50 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-28 04:25:50 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-28 04:25:50 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-28 04:25:50 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-28 04:25:50 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-28 04:25:50 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-28 04:25:50 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-28 04:25:50 (9414) [INFO]         or
* 2025-01-28 04:25:50 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-28 04:25:50 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-28 04:25:50 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-28 04:25:50 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-28 04:25:50 (9414) [INFO]         compromise:
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-28 04:25:50 (9414) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-28 04:25:50 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-28 04:25:50 (9431) [INFO] 
* 2025-01-28 04:25:50 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-28 04:25:50 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-28 04:25:50 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-28 04:25:50 (9401) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-28 04:25:50 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-28 04:25:50 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-28 04:25:50 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-28 04:25:50 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-28 04:25:50 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-28 04:25:50 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-28 04:25:50 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-28 04:25:50 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-28 04:25:50 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-28 04:25:50 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-28 04:25:50 (9431) [INFO] 
* 2025-01-28 04:25:50 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-28 04:25:50 (9401) [INFO] 
* 2025-01-28 04:25:50 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-28 04:25:51 (9414) [INFO] Determining fastest mirrors
* 2025-01-28 04:25:54 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-28 04:25:54 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-28 04:25:54 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-28 04:25:54 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-28 04:25:54 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-28 04:25:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-28 04:25:55 (9414) [INFO] Trying other mirror.
* 2025-01-28 04:25:55 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-28 04:25:55 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-28 04:25:55 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-28 04:25:55 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-28 04:25:55 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-28 04:25:55 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-28 04:25:55 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-28 04:25:55 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-28 04:25:55 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-28 04:25:55 (9414) [INFO]         or
* 2025-01-28 04:25:55 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-28 04:25:55 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-28 04:25:55 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-28 04:25:55 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-28 04:25:55 (9414) [INFO]         compromise:
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-28 04:25:55 (9414) [INFO] 
* 2025-01-28 04:25:55 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-28 04:25:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-28 04:25:55 (9431) [INFO] 
* 2025-01-28 04:25:55 (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-01-28 04:25:55 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-28 04:25:55 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-28 04:25:56 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_7l3SHmyHa/ea_profile.json
* 2025-01-28 04:25:58 (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/_7l3SHmyHa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-28 04:25:58 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-29 04:25:36 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-29 04:25:36 (10480) [INFO] Script is up to date.
* 2025-01-29 04:25:38 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-29 04:25:38 (9401) [INFO] 
* 2025-01-29 04:25:40 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-29 04:25:40 (9401) [INFO] 
* 2025-01-29 04:25:47 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-29 04:25:47 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-29 04:25:47 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-29 04:25:47 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-29 04:25:47 (9401) [INFO] 
* 2025-01-29 04:25:47 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-29 04:25:47 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-29 04:25:48 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-29 04:25:48 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-29 04:25:48 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-29 04:25:48 (9414) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-29 04:25:48 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-29 04:25:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-29 04:25:48 (9414) [INFO] Trying other mirror.
* 2025-01-29 04:25:48 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-29 04:25:48 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-29 04:25:48 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-29 04:25:48 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-29 04:25:48 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-29 04:25:48 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-29 04:25:48 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-29 04:25:48 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-29 04:25:48 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-29 04:25:48 (9414) [INFO]         or
* 2025-01-29 04:25:48 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-29 04:25:48 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-29 04:25:48 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-29 04:25:48 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-29 04:25:48 (9414) [INFO]         compromise:
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-29 04:25:48 (9414) [INFO] 
* 2025-01-29 04:25:48 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-29 04:25:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-29 04:25:48 (9431) [INFO] 
* 2025-01-29 04:25:48 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-29 04:25:48 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-29 04:25:48 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-29 04:25:48 (9401) [INFO] 
* 2025-01-29 04:25:49 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-29 04:25:49 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-29 04:25:49 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-29 04:25:49 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-29 04:25:49 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-29 04:25:49 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-29 04:25:49 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-29 04:25:49 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-29 04:25:49 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-29 04:25:49 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-29 04:25:49 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-29 04:25:49 (9431) [INFO] 
* 2025-01-29 04:25:49 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-29 04:25:49 (9401) [INFO] 
* 2025-01-29 04:25:49 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-29 04:25:49 (9414) [INFO] Determining fastest mirrors
* 2025-01-29 04:25:52 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-29 04:25:52 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-29 04:25:52 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-29 04:25:52 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-29 04:25:52 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-29 04:25:53 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-29 04:25:53 (9414) [INFO] Trying other mirror.
* 2025-01-29 04:25:53 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-29 04:25:53 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-29 04:25:53 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-29 04:25:53 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-29 04:25:53 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-29 04:25:53 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-29 04:25:53 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-29 04:25:53 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-29 04:25:53 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-29 04:25:53 (9414) [INFO]         or
* 2025-01-29 04:25:53 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-29 04:25:53 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-29 04:25:53 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-29 04:25:53 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-29 04:25:53 (9414) [INFO]         compromise:
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-29 04:25:53 (9414) [INFO] 
* 2025-01-29 04:25:53 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-29 04:25:53 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-29 04:25:53 (9431) [INFO] 
* 2025-01-29 04:25:53 (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-01-29 04:25:53 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-29 04:25:53 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-29 04:25:54 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FQKfsw4USm/ea_profile.json
* 2025-01-29 04:25:55 (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/FQKfsw4USm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-29 04:25:55 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-30 04:25:35 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-30 04:25:35 (10480) [INFO] Script is up to date.
* 2025-01-30 04:25:36 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-30 04:25:36 (9401) [INFO] 
* 2025-01-30 04:25:39 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-30 04:25:39 (9401) [INFO] 
* 2025-01-30 04:25:46 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-30 04:25:46 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-30 04:25:46 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-30 04:25:46 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-30 04:25:46 (9401) [INFO] 
* 2025-01-30 04:25:46 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-30 04:25:46 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-30 04:25:47 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-30 04:25:47 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-30 04:25:47 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-30 04:25:47 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-30 04:25:47 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-30 04:25:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-30 04:25:48 (9414) [INFO] Trying other mirror.
* 2025-01-30 04:25:48 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-30 04:25:48 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-30 04:25:48 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-30 04:25:48 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-30 04:25:48 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-30 04:25:48 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-30 04:25:48 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-30 04:25:48 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-30 04:25:48 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-30 04:25:48 (9414) [INFO]         or
* 2025-01-30 04:25:48 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-30 04:25:48 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-30 04:25:48 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-30 04:25:48 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-30 04:25:48 (9414) [INFO]         compromise:
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-30 04:25:48 (9414) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-30 04:25:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-30 04:25:48 (9431) [INFO] 
* 2025-01-30 04:25:48 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-30 04:25:48 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-30 04:25:48 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-30 04:25:48 (9401) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-30 04:25:48 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-30 04:25:48 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-30 04:25:48 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-30 04:25:48 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-30 04:25:48 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-30 04:25:48 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-30 04:25:48 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-30 04:25:48 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-30 04:25:48 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-30 04:25:48 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-30 04:25:48 (9431) [INFO] 
* 2025-01-30 04:25:48 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-30 04:25:48 (9401) [INFO] 
* 2025-01-30 04:25:48 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-30 04:25:49 (9414) [INFO] Determining fastest mirrors
* 2025-01-30 04:25:52 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-30 04:25:52 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-30 04:25:52 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-30 04:25:52 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-30 04:25:52 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-30 04:25:52 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-30 04:25:52 (9414) [INFO] Trying other mirror.
* 2025-01-30 04:25:52 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-30 04:25:52 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-30 04:25:52 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-30 04:25:52 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-30 04:25:52 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-30 04:25:52 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-30 04:25:52 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-30 04:25:52 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-30 04:25:52 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-30 04:25:52 (9414) [INFO]         or
* 2025-01-30 04:25:52 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-30 04:25:52 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-30 04:25:52 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-30 04:25:52 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-30 04:25:52 (9414) [INFO]         compromise:
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-30 04:25:52 (9414) [INFO] 
* 2025-01-30 04:25:52 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-30 04:25:52 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-30 04:25:52 (9431) [INFO] 
* 2025-01-30 04:25: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-01-30 04:25:52 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-30 04:25:53 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-30 04:25:53 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LxGZ20PRA_/ea_profile.json
* 2025-01-30 04:25:55 (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/LxGZ20PRA_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-30 04:25:55 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-31 04:25:35 (10458) [INFO] Self-update of script version 60 requested.
* 2025-01-31 04:25:35 (10480) [INFO] Script is up to date.
* 2025-01-31 04:25:36 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-31 04:25:36 (9401) [INFO] 
* 2025-01-31 04:25:38 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-01-31 04:25:38 (9401) [INFO] 
* 2025-01-31 04:25:48 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-01-31 04:25:48 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-01-31 04:25:48 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-01-31 04:25:48 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-31 04:25:48 (9401) [INFO] 
* 2025-01-31 04:25:49 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-31 04:25:49 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-31 04:25:50 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-31 04:25:50 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-31 04:25:50 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-31 04:25:50 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-31 04:25:50 (9414) [INFO]  * remi-safe: muug.ca
* 2025-01-31 04:25:50 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-31 04:25:50 (9414) [INFO] Trying other mirror.
* 2025-01-31 04:25:50 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-31 04:25:50 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-31 04:25:50 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-31 04:25:50 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-31 04:25:50 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-31 04:25:50 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-31 04:25:50 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-31 04:25:50 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-31 04:25:50 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-31 04:25:50 (9414) [INFO]         or
* 2025-01-31 04:25:50 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-31 04:25:50 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-31 04:25:50 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-31 04:25:50 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-31 04:25:50 (9414) [INFO]         compromise:
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-31 04:25:50 (9414) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-31 04:25:50 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-31 04:25:50 (9431) [INFO] 
* 2025-01-31 04:25:50 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-31 04:25:50 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-31 04:25:50 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-01-31 04:25:50 (9401) [INFO] 
* 2025-01-31 04:25:50 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-31 04:25:51 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-01-31 04:25:51 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-31 04:25:51 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-31 04:25:51 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-01-31 04:25:51 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-01-31 04:25:51 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-01-31 04:25:51 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-01-31 04:25:51 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-01-31 04:25:51 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-01-31 04:25:51 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-01-31 04:25:51 (9431) [INFO] 
* 2025-01-31 04:25:51 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-01-31 04:25:51 (9401) [INFO] 
* 2025-01-31 04:25:51 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-31 04:25:51 (9414) [INFO] Determining fastest mirrors
* 2025-01-31 04:25:54 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-01-31 04:25:54 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-31 04:25:54 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-31 04:25:54 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-31 04:25:54 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-31 04:25:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-31 04:25:55 (9414) [INFO] Trying other mirror.
* 2025-01-31 04:25:55 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-01-31 04:25:55 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-31 04:25:55 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-31 04:25:55 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-31 04:25:55 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-31 04:25:55 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-31 04:25:55 (9414) [INFO]             yum --disablerepo=base ...
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-31 04:25:55 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-31 04:25:55 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO]             yum-config-manager --disable base
* 2025-01-31 04:25:55 (9414) [INFO]         or
* 2025-01-31 04:25:55 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-31 04:25:55 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-31 04:25:55 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-31 04:25:55 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-31 04:25:55 (9414) [INFO]         compromise:
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-31 04:25:55 (9414) [INFO] 
* 2025-01-31 04:25:55 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-31 04:25:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-31 04:25:55 (9431) [INFO] 
* 2025-01-31 04:25:55 (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-01-31 04:25:55 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-31 04:25:55 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-31 04:25:56 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7OP0GxGX4l/ea_profile.json
* 2025-01-31 04:25:57 (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/7OP0GxGX4l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-31 04:25:57 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-01 04:26:35 (10458) [INFO] Self-update of script version 60 requested.
* 2025-02-01 04:26:35 (10480) [INFO] Script is up to date.
* 2025-02-01 04:26:36 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-01 04:26:36 (9401) [INFO] 
* 2025-02-01 04:26:39 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-02-01 04:26:39 (9401) [INFO] 
* 2025-02-01 04:26:47 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-01 04:26:47 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-01 04:26:47 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-01 04:26:47 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-01 04:26:47 (9401) [INFO] 
* 2025-02-01 04:26:47 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-01 04:26:47 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-01 04:26:48 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-01 04:26:48 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-01 04:26:48 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-01 04:26:48 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-01 04:26:48 (9414) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-02-01 04:26:49 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-01 04:26:49 (9414) [INFO] Trying other mirror.
* 2025-02-01 04:26:49 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-01 04:26:49 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-01 04:26:49 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-01 04:26:49 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-01 04:26:49 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-01 04:26:49 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-01 04:26:49 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-01 04:26:49 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-01 04:26:49 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-01 04:26:49 (9414) [INFO]         or
* 2025-02-01 04:26:49 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-01 04:26:49 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-01 04:26:49 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-01 04:26:49 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-01 04:26:49 (9414) [INFO]         compromise:
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-01 04:26:49 (9414) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-01 04:26:49 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-01 04:26:49 (9431) [INFO] 
* 2025-02-01 04:26:49 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-01 04:26:49 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-01 04:26:49 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-02-01 04:26:49 (9401) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-01 04:26:49 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-01 04:26:49 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-01 04:26:49 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-01 04:26:49 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-01 04:26:49 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-01 04:26:49 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-01 04:26:49 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-01 04:26:49 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-01 04:26:49 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-02-01 04:26:49 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-01 04:26:49 (9431) [INFO] 
* 2025-02-01 04:26:49 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-01 04:26:49 (9401) [INFO] 
* 2025-02-01 04:26:49 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-01 04:26:50 (9414) [INFO] Determining fastest mirrors
* 2025-02-01 04:26:53 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-01 04:26:53 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-01 04:26:53 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-01 04:26:53 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-01 04:26:53 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-01 04:26:53 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-01 04:26:53 (9414) [INFO] Trying other mirror.
* 2025-02-01 04:26:53 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-01 04:26:53 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-01 04:26:53 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-01 04:26:53 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-01 04:26:53 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-01 04:26:53 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-01 04:26:53 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-01 04:26:53 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-01 04:26:53 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-01 04:26:53 (9414) [INFO]         or
* 2025-02-01 04:26:53 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-01 04:26:53 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-01 04:26:53 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-01 04:26:53 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-01 04:26:53 (9414) [INFO]         compromise:
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-01 04:26:53 (9414) [INFO] 
* 2025-02-01 04:26:53 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-01 04:26:53 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-01 04:26:53 (9431) [INFO] 
* 2025-02-01 04:26:53 (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-01 04:26:53 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-01 04:26:54 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-01 04:26:54 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BYxaFzyKCb/ea_profile.json
* 2025-02-01 04:26: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/BYxaFzyKCb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-02-01 04:26:56 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-02 04:26:27 (10458) [INFO] Self-update of script version 60 requested.
* 2025-02-02 04:26:27 (10480) [INFO] Script is up to date.
* 2025-02-02 04:26:29 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-02 04:26:29 (9401) [INFO] 
* 2025-02-02 04:26:33 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-02-02 04:26:33 (9401) [INFO] 
* 2025-02-02 04:26:40 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-02 04:26:40 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-02 04:26:40 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-02 04:26:40 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-02 04:26:40 (9401) [INFO] 
* 2025-02-02 04:26:40 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-02 04:26:40 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-02 04:26:42 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-02 04:26:42 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-02 04:26:42 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-02 04:26:42 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-02 04:26:42 (9414) [INFO]  * remi-safe: muug.ca
* 2025-02-02 04:26:43 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-02 04:26:43 (9414) [INFO] Trying other mirror.
* 2025-02-02 04:26:43 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-02 04:26:43 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-02 04:26:43 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-02 04:26:43 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-02 04:26:43 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-02 04:26:43 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-02 04:26:43 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-02 04:26:43 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-02 04:26:43 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-02 04:26:43 (9414) [INFO]         or
* 2025-02-02 04:26:43 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-02 04:26:43 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-02 04:26:43 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-02 04:26:43 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-02 04:26:43 (9414) [INFO]         compromise:
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-02 04:26:43 (9414) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-02 04:26:43 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-02 04:26:43 (9431) [INFO] 
* 2025-02-02 04:26:43 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-02 04:26:43 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-02 04:26:43 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-02-02 04:26:43 (9401) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-02 04:26:43 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-02 04:26:43 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-02 04:26:43 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-02 04:26:43 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-02 04:26:43 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-02 04:26:43 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-02 04:26:43 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-02 04:26:43 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-02 04:26:43 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-02-02 04:26:43 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-02 04:26:43 (9431) [INFO] 
* 2025-02-02 04:26:43 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-02 04:26:43 (9401) [INFO] 
* 2025-02-02 04:26:43 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-02 04:26:43 (9414) [INFO] Determining fastest mirrors
* 2025-02-02 04:26:47 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-02 04:26:47 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-02 04:26:47 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-02 04:26:47 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-02 04:26:47 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-02 04:26:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-02 04:26:48 (9414) [INFO] Trying other mirror.
* 2025-02-02 04:26:48 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-02 04:26:48 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-02 04:26:48 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-02 04:26:48 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-02 04:26:48 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-02 04:26:48 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-02 04:26:48 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-02 04:26:48 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-02 04:26:48 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-02 04:26:48 (9414) [INFO]         or
* 2025-02-02 04:26:48 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-02 04:26:48 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-02 04:26:48 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-02 04:26:48 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-02 04:26:48 (9414) [INFO]         compromise:
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-02 04:26:48 (9414) [INFO] 
* 2025-02-02 04:26:48 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-02 04:26:48 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-02 04:26:48 (9431) [INFO] 
* 2025-02-02 04:26:48 (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 04:26:48 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-02 04:26:48 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-02 04:26:49 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TPKNSgpr3t/ea_profile.json
* 2025-02-02 04:26:51 (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/TPKNSgpr3t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-02-02 04:26:52 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-03 04:25:43 (10458) [INFO] Self-update of script version 60 requested.
* 2025-02-03 04:25:43 (10480) [INFO] Script is up to date.
* 2025-02-03 04:25:45 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-03 04:25:45 (9401) [INFO] 
* 2025-02-03 04:25:47 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-02-03 04:25:47 (9401) [INFO] 
* 2025-02-03 04:25:53 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-03 04:25:53 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-03 04:25:53 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-03 04:25:54 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-03 04:25:54 (9401) [INFO] 
* 2025-02-03 04:25:54 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-03 04:25:54 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-03 04:25:54 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-03 04:25:54 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-03 04:25:54 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-03 04:25:54 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-03 04:25:54 (9414) [INFO]  * remi-safe: muug.ca
* 2025-02-03 04:25:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-03 04:25:55 (9414) [INFO] Trying other mirror.
* 2025-02-03 04:25:55 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-03 04:25:55 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-03 04:25:55 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-03 04:25:55 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-03 04:25:55 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-03 04:25:55 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-03 04:25:55 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-03 04:25:55 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-03 04:25:55 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-03 04:25:55 (9414) [INFO]         or
* 2025-02-03 04:25:55 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-03 04:25:55 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-03 04:25:55 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-03 04:25:55 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-03 04:25:55 (9414) [INFO]         compromise:
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-03 04:25:55 (9414) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-03 04:25:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-03 04:25:55 (9431) [INFO] 
* 2025-02-03 04:25:55 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-03 04:25:55 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-03 04:25:55 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-02-03 04:25:55 (9401) [INFO] 
* 2025-02-03 04:25:55 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-03 04:25:56 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-03 04:25:56 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-03 04:25:56 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-03 04:25:56 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-03 04:25:56 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-03 04:25:56 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-03 04:25:56 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-03 04:25:56 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-03 04:25:56 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-02-03 04:25:56 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-03 04:25:56 (9431) [INFO] 
* 2025-02-03 04:25:56 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-03 04:25:56 (9401) [INFO] 
* 2025-02-03 04:25:56 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-03 04:25:56 (9414) [INFO] Determining fastest mirrors
* 2025-02-03 04:25:59 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-03 04:25:59 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-03 04:25:59 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-03 04:25:59 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-03 04:25:59 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-03 04:25:59 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-03 04:25:59 (9414) [INFO] Trying other mirror.
* 2025-02-03 04:25:59 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-03 04:25:59 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-03 04:25:59 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-03 04:25:59 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-03 04:25:59 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-03 04:25:59 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-03 04:25:59 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-03 04:25:59 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-03 04:25:59 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-03 04:25:59 (9414) [INFO]         or
* 2025-02-03 04:25:59 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-03 04:25:59 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-03 04:25:59 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-03 04:25:59 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-03 04:25:59 (9414) [INFO]         compromise:
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-03 04:25:59 (9414) [INFO] 
* 2025-02-03 04:25:59 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-03 04:25:59 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-03 04:25:59 (9431) [INFO] 
* 2025-02-03 04:25:59 (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 04:25:59 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-03 04:26:00 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-03 04:26:01 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6HDUT6xzZ5/ea_profile.json
* 2025-02-03 04:26:02 (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/6HDUT6xzZ5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-02-03 04:26:02 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-04 04:25:34 (10458) [INFO] Self-update of script version 60 requested.
* 2025-02-04 04:25:34 (10480) [INFO] Script is up to date.
* 2025-02-04 04:25:35 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-04 04:25:35 (9401) [INFO] 
* 2025-02-04 04:25:38 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-02-04 04:25:38 (9401) [INFO] 
* 2025-02-04 04:25:54 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-04 04:25:54 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-04 04:25:54 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-04 04:25:54 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-04 04:25:54 (9401) [INFO] 
* 2025-02-04 04:25:54 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-04 04:25:55 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-04 04:25:56 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-04 04:25:56 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-04 04:25:56 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-04 04:25:56 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-04 04:25:56 (9414) [INFO]  * remi-safe: muug.ca
* 2025-02-04 04:25:56 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-04 04:25:56 (9414) [INFO] Trying other mirror.
* 2025-02-04 04:25:56 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-04 04:25:56 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-04 04:25:56 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-04 04:25:56 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-04 04:25:56 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-04 04:25:56 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-04 04:25:56 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-04 04:25:56 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-04 04:25:56 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-04 04:25:56 (9414) [INFO]         or
* 2025-02-04 04:25:56 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-04 04:25:56 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-04 04:25:56 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-04 04:25:56 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-04 04:25:56 (9414) [INFO]         compromise:
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-04 04:25:56 (9414) [INFO] 
* 2025-02-04 04:25:56 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-04 04:25:56 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-04 04:25:56 (9431) [INFO] 
* 2025-02-04 04:25:56 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-04 04:25:56 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-04 04:25:56 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-02-04 04:25:56 (9401) [INFO] 
* 2025-02-04 04:25:57 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-04 04:25:57 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-04 04:25:57 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-04 04:25:57 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-04 04:25:57 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-04 04:25:57 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-04 04:25:57 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-04 04:25:57 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-04 04:25:57 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-04 04:25:57 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-02-04 04:25:57 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-04 04:25:57 (9431) [INFO] 
* 2025-02-04 04:25:57 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-04 04:25:57 (9401) [INFO] 
* 2025-02-04 04:25:57 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-04 04:25:57 (9414) [INFO] Determining fastest mirrors
* 2025-02-04 04:26:00 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-04 04:26:00 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-04 04:26:00 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-04 04:26:00 (9414) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-02-04 04:26:00 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-04 04:26:01 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-04 04:26:01 (9414) [INFO] Trying other mirror.
* 2025-02-04 04:26:01 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-04 04:26:01 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-04 04:26:01 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-04 04:26:01 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-04 04:26:01 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-04 04:26:01 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-04 04:26:01 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-04 04:26:01 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-04 04:26:01 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-04 04:26:01 (9414) [INFO]         or
* 2025-02-04 04:26:01 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-04 04:26:01 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-04 04:26:01 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-04 04:26:01 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-04 04:26:01 (9414) [INFO]         compromise:
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-04 04:26:01 (9414) [INFO] 
* 2025-02-04 04:26:01 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-04 04:26:01 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-04 04:26:01 (9431) [INFO] 
* 2025-02-04 04:26:01 (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-04 04:26:01 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-04 04:26:01 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-04 04:26:02 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/r3NpJnLOD3/ea_profile.json
* 2025-02-04 04:26:04 (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/r3NpJnLOD3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-02-04 04:26:04 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-05 04:25:36 (10458) [INFO] Self-update of script version 60 requested.
* 2025-02-05 04:25:36 (10480) [INFO] Script is up to date.
* 2025-02-05 04:25:37 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-05 04:25:37 (9401) [INFO] 
* 2025-02-05 04:25:40 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-02-05 04:25:40 (9401) [INFO] 
* 2025-02-05 04:25:47 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-05 04:25:47 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-05 04:25:47 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-05 04:25:47 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-05 04:25:47 (9401) [INFO] 
* 2025-02-05 04:25:47 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-05 04:25:47 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-05 04:25:49 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-05 04:25:49 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-05 04:25:49 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-05 04:25:49 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-05 04:25:49 (9414) [INFO]  * remi-safe: muug.ca
* 2025-02-05 04:25:50 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-05 04:25:50 (9414) [INFO] Trying other mirror.
* 2025-02-05 04:25:50 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-05 04:25:50 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-05 04:25:50 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-05 04:25:50 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-05 04:25:50 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-05 04:25:50 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-05 04:25:50 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-05 04:25:50 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-05 04:25:50 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-05 04:25:50 (9414) [INFO]         or
* 2025-02-05 04:25:50 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-05 04:25:50 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-05 04:25:50 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-05 04:25:50 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-05 04:25:50 (9414) [INFO]         compromise:
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-05 04:25:50 (9414) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-05 04:25:50 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-05 04:25:50 (9431) [INFO] 
* 2025-02-05 04:25:50 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-05 04:25:50 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-05 04:25:50 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-02-05 04:25:50 (9401) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-05 04:25:50 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-05 04:25:50 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-05 04:25:50 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-05 04:25:50 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-05 04:25:50 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-05 04:25:50 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-05 04:25:50 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-05 04:25:50 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-05 04:25:50 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-02-05 04:25:50 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-05 04:25:50 (9431) [INFO] 
* 2025-02-05 04:25:50 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-05 04:25:50 (9401) [INFO] 
* 2025-02-05 04:25:50 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-05 04:25:50 (9414) [INFO] Determining fastest mirrors
* 2025-02-05 04:25:54 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-05 04:25:54 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-05 04:25:54 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-05 04:25:54 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-05 04:25:54 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-05 04:25:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-05 04:25:55 (9414) [INFO] Trying other mirror.
* 2025-02-05 04:25:55 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-05 04:25:55 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-05 04:25:55 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-05 04:25:55 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-05 04:25:55 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-05 04:25:55 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-05 04:25:55 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-05 04:25:55 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-05 04:25:55 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-05 04:25:55 (9414) [INFO]         or
* 2025-02-05 04:25:55 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-05 04:25:55 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-05 04:25:55 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-05 04:25:55 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-05 04:25:55 (9414) [INFO]         compromise:
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-05 04:25:55 (9414) [INFO] 
* 2025-02-05 04:25:55 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-05 04:25:55 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-05 04:25:55 (9431) [INFO] 
* 2025-02-05 04:25:55 (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 04:25:55 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-05 04:25:55 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-05 04:25:56 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NmtWrinMZF/ea_profile.json
* 2025-02-05 04:25:58 (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/NmtWrinMZF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-02-05 04:25:58 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-06 04:25:34 (10458) [INFO] Self-update of script version 60 requested.
* 2025-02-06 04:25:34 (10480) [INFO] Script is up to date.
* 2025-02-06 04:25:35 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-06 04:25:35 (9401) [INFO] 
* 2025-02-06 04:25:38 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-02-06 04:25:38 (9401) [INFO] 
* 2025-02-06 04:25:45 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-06 04:25:45 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-06 04:25:45 (6019) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-06 04:25:45 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-06 04:25:45 (9401) [INFO] 
* 2025-02-06 04:25:45 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-06 04:25:45 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-06 04:25:46 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-06 04:25:46 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-06 04:25:46 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-06 04:25:46 (9414) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-02-06 04:25:46 (9414) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-02-06 04:25:47 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-06 04:25:47 (9414) [INFO] Trying other mirror.
* 2025-02-06 04:25:47 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-06 04:25:47 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-06 04:25:47 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-06 04:25:47 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-06 04:25:47 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-06 04:25:47 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-06 04:25:47 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-06 04:25:47 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-06 04:25:47 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-06 04:25:47 (9414) [INFO]         or
* 2025-02-06 04:25:47 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-06 04:25:47 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-06 04:25:47 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-06 04:25:47 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-06 04:25:47 (9414) [INFO]         compromise:
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-06 04:25:47 (9414) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-06 04:25:47 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-06 04:25:47 (9431) [INFO] 
* 2025-02-06 04:25:47 (5878) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-06 04:25:47 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-06 04:25:47 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-02-06 04:25:47 (9401) [INFO] 
* 2025-02-06 04:25:47 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-06 04:25:47 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-06 04:25:47 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-06 04:25:47 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-06 04:25:47 (9414) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-06 04:25:47 (9414) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-06 04:25:47 (9414) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-06 04:25:47 (9414) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-06 04:25:47 (9414) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-06 04:25:47 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-02-06 04:25:47 (9414) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-06 04:25:47 (9431) [INFO] 
* 2025-02-06 04:25:47 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-06 04:25:47 (9401) [INFO] 
* 2025-02-06 04:25:48 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-06 04:25:48 (9414) [INFO] Determining fastest mirrors
* 2025-02-06 04:25:51 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-06 04:25:51 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-06 04:25:51 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-06 04:25:51 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-06 04:25:51 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-06 04:25:51 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-06 04:25:51 (9414) [INFO] Trying other mirror.
* 2025-02-06 04:25:51 (9414) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-06 04:25:51 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-06 04:25:51 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-06 04:25:51 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-06 04:25:51 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-06 04:25:51 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-06 04:25:51 (9414) [INFO]             yum --disablerepo=base ...
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-06 04:25:51 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-06 04:25:51 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO]             yum-config-manager --disable base
* 2025-02-06 04:25:51 (9414) [INFO]         or
* 2025-02-06 04:25:51 (9414) [INFO]             subscription-manager repos --disable=base
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-06 04:25:51 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-06 04:25:51 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-06 04:25:51 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-06 04:25:51 (9414) [INFO]         compromise:
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-06 04:25:51 (9414) [INFO] 
* 2025-02-06 04:25:51 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-06 04:25:51 (9414) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-06 04:25:51 (9431) [INFO] 
* 2025-02-06 04:25:51 (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-06 04:25:51 (5889) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-06 04:25:52 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-06 04:25:53 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JKjgrrRQ2X/ea_profile.json
* 2025-02-06 04:25:54 (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/JKjgrrRQ2X/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-02-06 04:25:54 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-07 04:25:40 (10458) [INFO] Self-update of script version 60 requested.
* 2025-02-07 04:25:40 (10463) [INFO] Newer version of script found. Downloading.
* 2025-02-07 04:25:41 (10472) [INFO] Script update to version 61 successful.
* 2025-02-07 04:25:42 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-07 04:25:42 (9407) [INFO] 
* 2025-02-07 04:25:45 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-07 04:25:45 (9407) [INFO] 
* 2025-02-07 04:26:00 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-07 04:26:00 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-07 04:26:00 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-07 04:26:00 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-07 04:26:00 (9407) [INFO] 
* 2025-02-07 04:26:00 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-07 04:26:01 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-07 04:26:02 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-07 04:26:02 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-07 04:26:02 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-07 04:26:02 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-07 04:26:02 (9420) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-02-07 04:26:03 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-07 04:26:03 (9420) [INFO] Trying other mirror.
* 2025-02-07 04:26:03 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-07 04:26:03 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-07 04:26:03 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-07 04:26:03 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-07 04:26:03 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-07 04:26:03 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-07 04:26:03 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-07 04:26:03 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-07 04:26:03 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-07 04:26:03 (9420) [INFO]         or
* 2025-02-07 04:26:03 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-07 04:26:03 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-07 04:26:03 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-07 04:26:03 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-07 04:26:03 (9420) [INFO]         compromise:
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-07 04:26:03 (9420) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-07 04:26:03 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-07 04:26:03 (9437) [INFO] 
* 2025-02-07 04:26:03 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-07 04:26:03 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-07 04:26:03 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-07 04:26:03 (9407) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-07 04:26:03 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-07 04:26:03 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-07 04:26:03 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-07 04:26:03 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-07 04:26:03 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-07 04:26:03 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-07 04:26:03 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-07 04:26:03 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-07 04:26:03 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-07 04:26:03 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-07 04:26:03 (9437) [INFO] 
* 2025-02-07 04:26:03 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-07 04:26:03 (9407) [INFO] 
* 2025-02-07 04:26:03 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-07 04:26:04 (9420) [INFO] Determining fastest mirrors
* 2025-02-07 04:26:07 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-07 04:26:07 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-07 04:26:07 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-07 04:26:07 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-07 04:26:07 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-07 04:26:08 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-07 04:26:08 (9420) [INFO] Trying other mirror.
* 2025-02-07 04:26:08 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-07 04:26:08 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-07 04:26:08 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-07 04:26:08 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-07 04:26:08 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-07 04:26:08 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-07 04:26:08 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-07 04:26:08 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-07 04:26:08 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-07 04:26:08 (9420) [INFO]         or
* 2025-02-07 04:26:08 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-07 04:26:08 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-07 04:26:08 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-07 04:26:08 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-07 04:26:08 (9420) [INFO]         compromise:
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-07 04:26:08 (9420) [INFO] 
* 2025-02-07 04:26:08 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-07 04:26:08 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-07 04:26:08 (9437) [INFO] 
* 2025-02-07 04:26:08 (5894) [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-07 04:26:08 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-07 04:26:08 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-07 04:26:09 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SPXwo7dggP/ea_profile.json
* 2025-02-07 04:26:11 (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/SPXwo7dggP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-07 04:26:11 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-08 04:26:23 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-08 04:26:24 (10486) [INFO] Script is up to date.
* 2025-02-08 04:26:25 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-08 04:26:25 (9407) [INFO] 
* 2025-02-08 04:26:28 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-08 04:26:28 (9407) [INFO] 
* 2025-02-08 04:26:36 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-08 04:26:36 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-08 04:26:36 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-08 04:26:36 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-08 04:26:36 (9407) [INFO] 
* 2025-02-08 04:26:36 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-08 04:26:36 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-08 04:26:38 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-08 04:26:38 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-08 04:26:38 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-08 04:26:38 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-08 04:26:38 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-08 04:26:38 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-08 04:26:38 (9420) [INFO] Trying other mirror.
* 2025-02-08 04:26:38 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-08 04:26:38 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-08 04:26:38 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-08 04:26:38 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-08 04:26:38 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-08 04:26:38 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-08 04:26:38 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-08 04:26:38 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-08 04:26:38 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-08 04:26:38 (9420) [INFO]         or
* 2025-02-08 04:26:38 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-08 04:26:38 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-08 04:26:38 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-08 04:26:38 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-08 04:26:38 (9420) [INFO]         compromise:
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-08 04:26:38 (9420) [INFO] 
* 2025-02-08 04:26:38 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-08 04:26:38 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-08 04:26:38 (9437) [INFO] 
* 2025-02-08 04:26:38 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-08 04:26:38 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-08 04:26:38 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-08 04:26:38 (9407) [INFO] 
* 2025-02-08 04:26:39 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-08 04:26:39 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-08 04:26:39 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-08 04:26:39 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-08 04:26:39 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-08 04:26:39 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-08 04:26:39 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-08 04:26:39 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-08 04:26:39 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-08 04:26:39 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-08 04:26:39 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-08 04:26:39 (9437) [INFO] 
* 2025-02-08 04:26:39 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-08 04:26:39 (9407) [INFO] 
* 2025-02-08 04:26:39 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-08 04:26:39 (9420) [INFO] Determining fastest mirrors
* 2025-02-08 04:26:43 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-08 04:26:43 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-08 04:26:43 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-08 04:26:43 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-08 04:26:43 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-08 04:26:44 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-08 04:26:44 (9420) [INFO] Trying other mirror.
* 2025-02-08 04:26:44 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-08 04:26:44 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-08 04:26:44 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-08 04:26:44 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-08 04:26:44 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-08 04:26:44 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-08 04:26:44 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-08 04:26:44 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-08 04:26:44 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-08 04:26:44 (9420) [INFO]         or
* 2025-02-08 04:26:44 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-08 04:26:44 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-08 04:26:44 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-08 04:26:44 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-08 04:26:44 (9420) [INFO]         compromise:
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-08 04:26:44 (9420) [INFO] 
* 2025-02-08 04:26:44 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-08 04:26:44 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-08 04:26:44 (9437) [INFO] 
* 2025-02-08 04:26:44 (5894) [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-08 04:26:44 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-08 04:26:44 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-08 04:26:45 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hfBJV64rV3/ea_profile.json
* 2025-02-08 04:26:48 (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/hfBJV64rV3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-08 04:26:48 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-09 04:26:24 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-09 04:26:24 (10486) [INFO] Script is up to date.
* 2025-02-09 04:26:26 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-09 04:26:26 (9407) [INFO] 
* 2025-02-09 04:26:29 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-09 04:26:29 (9407) [INFO] 
* 2025-02-09 04:26:43 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-09 04:26:43 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-09 04:26:43 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-09 04:26:43 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-09 04:26:43 (9407) [INFO] 
* 2025-02-09 04:26:43 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-09 04:26:43 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-09 04:26:44 (9420) [INFO]  * EA4: 63.247.64.58
* 2025-02-09 04:26:44 (9420) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-02-09 04:26:44 (9420) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-02-09 04:26:44 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-09 04:26:44 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-09 04:26:45 (9420) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
* 2025-02-09 04:26:45 (9420) [INFO] Trying other mirror.
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO]  One of the configured repositories failed (MariaDB103),
* 2025-02-09 04:26:45 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-09 04:26:45 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-09 04:26:45 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-09 04:26:45 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-09 04:26:45 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-09 04:26:45 (9420) [INFO]             yum --disablerepo=MariaDB103 ...
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-09 04:26:45 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-09 04:26:45 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO]             yum-config-manager --disable MariaDB103
* 2025-02-09 04:26:45 (9420) [INFO]         or
* 2025-02-09 04:26:45 (9420) [INFO]             subscription-manager repos --disable=MariaDB103
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-09 04:26:45 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-09 04:26:45 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-09 04:26:45 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-09 04:26:45 (9420) [INFO]         compromise:
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO]             yum-config-manager --save --setopt=MariaDB103.skip_if_unavailable=true
* 2025-02-09 04:26:45 (9420) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO] failure: repodata/repomd.xml from MariaDB103: [Errno 256] No more mirrors to try.
* 2025-02-09 04:26:45 (9420) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
* 2025-02-09 04:26:45 (9437) [INFO] 
* 2025-02-09 04:26:45 (5884) [WARN] Initial run of "yum makecache" failed: https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
Trying other mirror.


 One of the configured repositories failed (MariaDB103),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=MariaDB103 ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable MariaDB103
        or
            subscription-manager repos --disable=MariaDB103

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=MariaDB103.skip_if_unavailable=true

failure: repodata/repomd.xml from MariaDB103: [Errno 256] No more mirrors to try.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
* 2025-02-09 04:26:45 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-09 04:26:45 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-09 04:26:45 (9407) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-09 04:26:45 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-09 04:26:45 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-09 04:26:45 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-09 04:26:45 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-09 04:26:45 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-09 04:26:45 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-09 04:26:45 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-09 04:26:45 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-09 04:26:45 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-09 04:26:45 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-09 04:26:45 (9437) [INFO] 
* 2025-02-09 04:26:45 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-09 04:26:45 (9407) [INFO] 
* 2025-02-09 04:26:45 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-09 04:26:45 (9420) [INFO] Determining fastest mirrors
* 2025-02-09 04:26:49 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-09 04:26:49 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-09 04:26:49 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-09 04:26:49 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-09 04:26:49 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-09 04:26:49 (9420) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
* 2025-02-09 04:26:49 (9420) [INFO] Trying other mirror.
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO]  One of the configured repositories failed (MariaDB103),
* 2025-02-09 04:26:49 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-09 04:26:49 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-09 04:26:49 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-09 04:26:49 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-09 04:26:49 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-09 04:26:49 (9420) [INFO]             yum --disablerepo=MariaDB103 ...
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-09 04:26:49 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-09 04:26:49 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO]             yum-config-manager --disable MariaDB103
* 2025-02-09 04:26:49 (9420) [INFO]         or
* 2025-02-09 04:26:49 (9420) [INFO]             subscription-manager repos --disable=MariaDB103
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-09 04:26:49 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-09 04:26:49 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-09 04:26:49 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-09 04:26:49 (9420) [INFO]         compromise:
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO]             yum-config-manager --save --setopt=MariaDB103.skip_if_unavailable=true
* 2025-02-09 04:26:49 (9420) [INFO] 
* 2025-02-09 04:26:49 (9420) [INFO] failure: repodata/repomd.xml from MariaDB103: [Errno 256] No more mirrors to try.
* 2025-02-09 04:26:49 (9420) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
* 2025-02-09 04:26:49 (9437) [INFO] 
* 2025-02-09 04:26:49 (5894) [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-09 04:26:49 (5895) [ERROR] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
Trying other mirror.


 One of the configured repositories failed (MariaDB103),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=MariaDB103 ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable MariaDB103
        or
            subscription-manager repos --disable=MariaDB103

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=MariaDB103.skip_if_unavailable=true

failure: repodata/repomd.xml from MariaDB103: [Errno 256] No more mirrors to try.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
* 2025-02-09 04:26:49 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-09 04:26:50 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fEVdE6SewE/ea_profile.json
* 2025-02-09 04:26:52 (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/fEVdE6SewE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-09 04:26:52 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-10 04:25:37 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-10 04:25:37 (10486) [INFO] Script is up to date.
* 2025-02-10 04:25:38 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-10 04:25:38 (9407) [INFO] 
* 2025-02-10 04:25:41 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-10 04:25:41 (9407) [INFO] 
* 2025-02-10 04:25:48 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-10 04:25:48 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-10 04:25:48 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-10 04:25:48 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-10 04:25:48 (9407) [INFO] 
* 2025-02-10 04:25:48 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-10 04:25:48 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-10 04:25:49 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-10 04:25:49 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-10 04:25:49 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-10 04:25:49 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-10 04:25:49 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-10 04:25:50 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-10 04:25:50 (9420) [INFO] Trying other mirror.
* 2025-02-10 04:25:50 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-10 04:25:50 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-10 04:25:50 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-10 04:25:50 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-10 04:25:50 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-10 04:25:50 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-10 04:25:50 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-10 04:25:50 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-10 04:25:50 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-10 04:25:50 (9420) [INFO]         or
* 2025-02-10 04:25:50 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-10 04:25:50 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-10 04:25:50 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-10 04:25:50 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-10 04:25:50 (9420) [INFO]         compromise:
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-10 04:25:50 (9420) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-10 04:25:50 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-10 04:25:50 (9437) [INFO] 
* 2025-02-10 04:25:50 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-10 04:25:50 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-10 04:25:50 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-10 04:25:50 (9407) [INFO] 
* 2025-02-10 04:25:50 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-10 04:25:50 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-10 04:25:50 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-10 04:25:50 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-10 04:25:50 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-10 04:25:50 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-10 04:25:50 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-10 04:25:50 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-10 04:25:50 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-10 04:25:50 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-10 04:25:50 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-10 04:25:50 (9437) [INFO] 
* 2025-02-10 04:25:50 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-10 04:25:50 (9407) [INFO] 
* 2025-02-10 04:25:51 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-10 04:25:51 (9420) [INFO] Determining fastest mirrors
* 2025-02-10 04:25:56 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-10 04:25:56 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-10 04:25:56 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-10 04:25:56 (9420) [INFO]  * epel: dl.fedoraproject.org
* 2025-02-10 04:25:56 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-10 04:25:56 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-10 04:25:56 (9420) [INFO] Trying other mirror.
* 2025-02-10 04:25:56 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-10 04:25:56 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-10 04:25:56 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-10 04:25:56 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-10 04:25:56 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-10 04:25:56 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-10 04:25:56 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-10 04:25:56 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-10 04:25:56 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-10 04:25:56 (9420) [INFO]         or
* 2025-02-10 04:25:56 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-10 04:25:56 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-10 04:25:56 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-10 04:25:56 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-10 04:25:56 (9420) [INFO]         compromise:
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-10 04:25:56 (9420) [INFO] 
* 2025-02-10 04:25:56 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-10 04:25:56 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-10 04:25:57 (9437) [INFO] 
* 2025-02-10 04:25:57 (5894) [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-10 04:25:57 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-10 04:25:57 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-10 04:25:58 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_GSnGUlyrA/ea_profile.json
* 2025-02-10 04:26:00 (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/_GSnGUlyrA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-10 04:26:00 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-11 04:25:35 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-11 04:25:35 (10486) [INFO] Script is up to date.
* 2025-02-11 04:25:36 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-11 04:25:36 (9407) [INFO] 
* 2025-02-11 04:25:38 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-11 04:25:38 (9407) [INFO] 
* 2025-02-11 04:25:45 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-11 04:25:45 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-11 04:25:45 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-11 04:25:45 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-11 04:25:45 (9407) [INFO] 
* 2025-02-11 04:25:45 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-11 04:25:45 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-11 04:25:47 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-11 04:25:47 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-11 04:25:47 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-11 04:25:47 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-11 04:25:47 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-11 04:25:47 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-11 04:25:47 (9420) [INFO] Trying other mirror.
* 2025-02-11 04:25:47 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-11 04:25:47 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-11 04:25:47 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-11 04:25:47 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-11 04:25:47 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-11 04:25:47 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-11 04:25:47 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-11 04:25:47 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-11 04:25:47 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-11 04:25:47 (9420) [INFO]         or
* 2025-02-11 04:25:47 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-11 04:25:47 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-11 04:25:47 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-11 04:25:47 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-11 04:25:47 (9420) [INFO]         compromise:
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-11 04:25:47 (9420) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-11 04:25:47 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-11 04:25:47 (9437) [INFO] 
* 2025-02-11 04:25:47 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-11 04:25:47 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-11 04:25:47 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-11 04:25:47 (9407) [INFO] 
* 2025-02-11 04:25:47 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-11 04:25:48 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-11 04:25:48 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-11 04:25:48 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-11 04:25:48 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-11 04:25:48 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-11 04:25:48 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-11 04:25:48 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-11 04:25:48 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-11 04:25:48 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-11 04:25:48 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-11 04:25:48 (9437) [INFO] 
* 2025-02-11 04:25:48 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-11 04:25:48 (9407) [INFO] 
* 2025-02-11 04:25:48 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-11 04:25:48 (9420) [INFO] Determining fastest mirrors
* 2025-02-11 04:25:52 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-11 04:25:52 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-11 04:25:52 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-11 04:25:52 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-11 04:25:52 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-11 04:25:52 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-11 04:25:52 (9420) [INFO] Trying other mirror.
* 2025-02-11 04:25:52 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-11 04:25:52 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-11 04:25:52 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-11 04:25:52 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-11 04:25:52 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-11 04:25:52 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-11 04:25:52 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-11 04:25:52 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-11 04:25:52 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-11 04:25:52 (9420) [INFO]         or
* 2025-02-11 04:25:52 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-11 04:25:52 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-11 04:25:52 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-11 04:25:52 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-11 04:25:52 (9420) [INFO]         compromise:
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-11 04:25:52 (9420) [INFO] 
* 2025-02-11 04:25:52 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-11 04:25:52 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-11 04:25:52 (9437) [INFO] 
* 2025-02-11 04:25:52 (5894) [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-11 04:25:52 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-11 04:25:53 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-11 04:25:53 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RmfU7rjJ1h/ea_profile.json
* 2025-02-11 04:25: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/RmfU7rjJ1h/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-11 04:25:56 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-12 04:25:49 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-12 04:25:49 (10486) [INFO] Script is up to date.
* 2025-02-12 04:25:50 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-12 04:25:50 (9407) [INFO] 
* 2025-02-12 04:25:52 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-12 04:25:52 (9407) [INFO] 
* 2025-02-12 04:25:59 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-12 04:25:59 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-12 04:25:59 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-12 04:25:59 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-12 04:25:59 (9407) [INFO] 
* 2025-02-12 04:25:59 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-12 04:25:59 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-12 04:26:00 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-12 04:26:00 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-12 04:26:00 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-12 04:26:00 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-12 04:26:00 (9420) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-02-12 04:26:01 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-12 04:26:01 (9420) [INFO] Trying other mirror.
* 2025-02-12 04:26:01 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-12 04:26:01 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-12 04:26:01 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-12 04:26:01 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-12 04:26:01 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-12 04:26:01 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-12 04:26:01 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-12 04:26:01 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-12 04:26:01 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-12 04:26:01 (9420) [INFO]         or
* 2025-02-12 04:26:01 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-12 04:26:01 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-12 04:26:01 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-12 04:26:01 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-12 04:26:01 (9420) [INFO]         compromise:
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-12 04:26:01 (9420) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-12 04:26:01 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-12 04:26:01 (9437) [INFO] 
* 2025-02-12 04:26:01 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-12 04:26:01 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-12 04:26:01 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-12 04:26:01 (9407) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-12 04:26:01 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-12 04:26:01 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-12 04:26:01 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-12 04:26:01 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-12 04:26:01 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-12 04:26:01 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-12 04:26:01 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-12 04:26:01 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-12 04:26:01 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-12 04:26:01 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-12 04:26:01 (9437) [INFO] 
* 2025-02-12 04:26:01 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-12 04:26:01 (9407) [INFO] 
* 2025-02-12 04:26:01 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-12 04:26:01 (9420) [INFO] Determining fastest mirrors
* 2025-02-12 04:26:04 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-12 04:26:04 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-12 04:26:04 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-12 04:26:04 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-12 04:26:04 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-12 04:26:05 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-12 04:26:05 (9420) [INFO] Trying other mirror.
* 2025-02-12 04:26:05 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-12 04:26:05 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-12 04:26:05 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-12 04:26:05 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-12 04:26:05 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-12 04:26:05 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-12 04:26:05 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-12 04:26:05 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-12 04:26:05 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-12 04:26:05 (9420) [INFO]         or
* 2025-02-12 04:26:05 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-12 04:26:05 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-12 04:26:05 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-12 04:26:05 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-12 04:26:05 (9420) [INFO]         compromise:
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-12 04:26:05 (9420) [INFO] 
* 2025-02-12 04:26:05 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-12 04:26:05 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-12 04:26:05 (9437) [INFO] 
* 2025-02-12 04:26:05 (5894) [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-12 04:26:05 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-12 04:26:05 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-12 04:26:06 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MUOtJzrH9W/ea_profile.json
* 2025-02-12 04:26:08 (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/MUOtJzrH9W/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-12 04:26:08 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-13 04:25:36 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-13 04:25:36 (10486) [INFO] Script is up to date.
* 2025-02-13 04:25:37 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-13 04:25:37 (9407) [INFO] 
* 2025-02-13 04:25:40 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-13 04:25:40 (9407) [INFO] 
* 2025-02-13 04:25:46 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-13 04:25:46 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-13 04:25:46 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-13 04:25:46 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-13 04:25:46 (9407) [INFO] 
* 2025-02-13 04:25:46 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-13 04:25:46 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-13 04:25:47 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-13 04:25:47 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-13 04:25:47 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-13 04:25:47 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-13 04:25:47 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-13 04:25:48 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-13 04:25:48 (9420) [INFO] Trying other mirror.
* 2025-02-13 04:25:48 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-13 04:25:48 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-13 04:25:48 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-13 04:25:48 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-13 04:25:48 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-13 04:25:48 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-13 04:25:48 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-13 04:25:48 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-13 04:25:48 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-13 04:25:48 (9420) [INFO]         or
* 2025-02-13 04:25:48 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-13 04:25:48 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-13 04:25:48 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-13 04:25:48 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-13 04:25:48 (9420) [INFO]         compromise:
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-13 04:25:48 (9420) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-13 04:25:48 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-13 04:25:48 (9437) [INFO] 
* 2025-02-13 04:25:48 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-13 04:25:48 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-13 04:25:48 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-13 04:25:48 (9407) [INFO] 
* 2025-02-13 04:25:48 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-13 04:25:48 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-13 04:25:48 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-13 04:25:48 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-13 04:25:48 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-13 04:25:48 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-13 04:25:48 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-13 04:25:48 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-13 04:25:48 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-13 04:25:48 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-13 04:25:48 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-13 04:25:48 (9437) [INFO] 
* 2025-02-13 04:25:48 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-13 04:25:48 (9407) [INFO] 
* 2025-02-13 04:25:49 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-13 04:25:49 (9420) [INFO] Determining fastest mirrors
* 2025-02-13 04:25:52 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-13 04:25:52 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-13 04:25:52 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-13 04:25:52 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-13 04:25:52 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-13 04:25:52 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-13 04:25:52 (9420) [INFO] Trying other mirror.
* 2025-02-13 04:25:52 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-13 04:25:52 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-13 04:25:52 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-13 04:25:52 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-13 04:25:52 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-13 04:25:52 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-13 04:25:52 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-13 04:25:52 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-13 04:25:52 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-13 04:25:52 (9420) [INFO]         or
* 2025-02-13 04:25:52 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-13 04:25:52 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-13 04:25:52 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-13 04:25:52 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-13 04:25:52 (9420) [INFO]         compromise:
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-13 04:25:52 (9420) [INFO] 
* 2025-02-13 04:25:52 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-13 04:25:52 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-13 04:25:53 (9437) [INFO] 
* 2025-02-13 04:25:53 (5894) [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-13 04:25:53 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-13 04:25:53 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-13 04:25:54 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RaKeQBAZX5/ea_profile.json
* 2025-02-13 04:25: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/RaKeQBAZX5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-13 04:25:56 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-14 04:25:47 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-14 04:25:47 (10486) [INFO] Script is up to date.
* 2025-02-14 04:25:48 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-14 04:25:48 (9407) [INFO] 
* 2025-02-14 04:25:50 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-14 04:25:50 (9407) [INFO] 
* 2025-02-14 04:26:02 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-14 04:26:02 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-14 04:26:02 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-14 04:26:02 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-14 04:26:02 (9407) [INFO] 
* 2025-02-14 04:26:02 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-14 04:26:02 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-14 04:26:04 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-14 04:26:04 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-14 04:26:04 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-14 04:26:04 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-14 04:26:04 (9420) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-02-14 04:26:04 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-14 04:26:04 (9420) [INFO] Trying other mirror.
* 2025-02-14 04:26:04 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-14 04:26:04 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-14 04:26:04 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-14 04:26:04 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-14 04:26:04 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-14 04:26:04 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-14 04:26:04 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-14 04:26:04 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-14 04:26:04 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-14 04:26:04 (9420) [INFO]         or
* 2025-02-14 04:26:04 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-14 04:26:04 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-14 04:26:04 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-14 04:26:04 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-14 04:26:04 (9420) [INFO]         compromise:
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-14 04:26:04 (9420) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-14 04:26:04 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-14 04:26:04 (9437) [INFO] 
* 2025-02-14 04:26:04 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-14 04:26:04 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-14 04:26:04 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-14 04:26:04 (9407) [INFO] 
* 2025-02-14 04:26:04 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-14 04:26:05 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-14 04:26:05 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-14 04:26:05 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-14 04:26:05 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-14 04:26:05 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-14 04:26:05 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-14 04:26:05 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-14 04:26:05 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-14 04:26:05 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-14 04:26:05 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-14 04:26:05 (9437) [INFO] 
* 2025-02-14 04:26:05 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-14 04:26:05 (9407) [INFO] 
* 2025-02-14 04:26:05 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-14 04:26:05 (9420) [INFO] Determining fastest mirrors
* 2025-02-14 04:26:10 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-14 04:26:10 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-14 04:26:10 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-14 04:26:10 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-14 04:26:10 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-14 04:26:10 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-14 04:26:10 (9420) [INFO] Trying other mirror.
* 2025-02-14 04:26:10 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-14 04:26:10 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-14 04:26:10 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-14 04:26:10 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-14 04:26:10 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-14 04:26:10 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-14 04:26:10 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-14 04:26:10 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-14 04:26:10 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-14 04:26:10 (9420) [INFO]         or
* 2025-02-14 04:26:10 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-14 04:26:10 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-14 04:26:10 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-14 04:26:10 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-14 04:26:10 (9420) [INFO]         compromise:
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-14 04:26:10 (9420) [INFO] 
* 2025-02-14 04:26:10 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-14 04:26:10 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-14 04:26:10 (9437) [INFO] 
* 2025-02-14 04:26:10 (5894) [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-14 04:26:10 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-14 04:26:10 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-14 04:26:11 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/htNicpjanG/ea_profile.json
* 2025-02-14 04:26:13 (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/htNicpjanG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-14 04:26:13 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-15 04:26:26 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-15 04:26:26 (10486) [INFO] Script is up to date.
* 2025-02-15 04:26:28 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-15 04:26:28 (9407) [INFO] 
* 2025-02-15 04:26:31 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-15 04:26:31 (9407) [INFO] 
* 2025-02-15 04:26:38 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-15 04:26:38 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-15 04:26:38 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-15 04:26:38 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-15 04:26:38 (9407) [INFO] 
* 2025-02-15 04:26:39 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-15 04:26:39 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-15 04:26:40 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-15 04:26:40 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-15 04:26:40 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-15 04:26:40 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-15 04:26:40 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-15 04:26:40 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-15 04:26:40 (9420) [INFO] Trying other mirror.
* 2025-02-15 04:26:40 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-15 04:26:40 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-15 04:26:40 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-15 04:26:40 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-15 04:26:40 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-15 04:26:40 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-15 04:26:40 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-15 04:26:40 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-15 04:26:40 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-15 04:26:40 (9420) [INFO]         or
* 2025-02-15 04:26:40 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-15 04:26:40 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-15 04:26:40 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-15 04:26:40 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-15 04:26:40 (9420) [INFO]         compromise:
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-15 04:26:40 (9420) [INFO] 
* 2025-02-15 04:26:40 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-15 04:26:40 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-15 04:26:40 (9437) [INFO] 
* 2025-02-15 04:26:40 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-15 04:26:40 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-15 04:26:40 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-15 04:26:40 (9407) [INFO] 
* 2025-02-15 04:26:41 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-15 04:26:41 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-15 04:26:41 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-15 04:26:41 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-15 04:26:41 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-15 04:26:41 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-15 04:26:41 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-15 04:26:41 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-15 04:26:41 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-15 04:26:41 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-15 04:26:41 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-15 04:26:41 (9437) [INFO] 
* 2025-02-15 04:26:41 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-15 04:26:41 (9407) [INFO] 
* 2025-02-15 04:26:41 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-15 04:26:41 (9420) [INFO] Determining fastest mirrors
* 2025-02-15 04:26:44 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-15 04:26:44 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-15 04:26:44 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-15 04:26:44 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-15 04:26:44 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-15 04:26:45 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-15 04:26:45 (9420) [INFO] Trying other mirror.
* 2025-02-15 04:26:45 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-15 04:26:45 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-15 04:26:45 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-15 04:26:45 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-15 04:26:45 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-15 04:26:45 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-15 04:26:45 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-15 04:26:45 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-15 04:26:45 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-15 04:26:45 (9420) [INFO]         or
* 2025-02-15 04:26:45 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-15 04:26:45 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-15 04:26:45 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-15 04:26:45 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-15 04:26:45 (9420) [INFO]         compromise:
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-15 04:26:45 (9420) [INFO] 
* 2025-02-15 04:26:45 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-15 04:26:45 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-15 04:26:45 (9437) [INFO] 
* 2025-02-15 04:26:45 (5894) [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-15 04:26:45 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-15 04:26:45 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-15 04:26:46 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eicPqFRxPp/ea_profile.json
* 2025-02-15 04:26:48 (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/eicPqFRxPp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-15 04:26:48 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-16 04:26:27 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-16 04:26:28 (10486) [INFO] Script is up to date.
* 2025-02-16 04:26:29 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-16 04:26:29 (9407) [INFO] 
* 2025-02-16 04:26:32 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-16 04:26:32 (9407) [INFO] 
* 2025-02-16 04:26:40 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-16 04:26:40 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-16 04:26:40 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-16 04:26:40 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-16 04:26:40 (9407) [INFO] 
* 2025-02-16 04:26:40 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-16 04:26:40 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-16 04:26:41 (9420) [INFO]  * EA4: 63.247.64.58
* 2025-02-16 04:26:41 (9420) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-02-16 04:26:41 (9420) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-02-16 04:26:41 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-16 04:26:41 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-16 04:26:41 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-16 04:26:41 (9420) [INFO] Trying other mirror.
* 2025-02-16 04:26:41 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-16 04:26:41 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-16 04:26:41 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-16 04:26:41 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-16 04:26:41 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-16 04:26:41 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-16 04:26:41 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-16 04:26:41 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-16 04:26:41 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-16 04:26:41 (9420) [INFO]         or
* 2025-02-16 04:26:41 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-16 04:26:41 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-16 04:26:41 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-16 04:26:41 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-16 04:26:41 (9420) [INFO]         compromise:
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-16 04:26:41 (9420) [INFO] 
* 2025-02-16 04:26:41 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-16 04:26:41 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-16 04:26:41 (9437) [INFO] 
* 2025-02-16 04:26:41 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-16 04:26:41 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-16 04:26:41 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-16 04:26:41 (9407) [INFO] 
* 2025-02-16 04:26:42 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-16 04:26:42 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-16 04:26:42 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-16 04:26:42 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-16 04:26:42 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-16 04:26:42 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-16 04:26:42 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-16 04:26:42 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-16 04:26:42 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-16 04:26:42 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-16 04:26:42 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-16 04:26:42 (9437) [INFO] 
* 2025-02-16 04:26:42 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-16 04:26:42 (9407) [INFO] 
* 2025-02-16 04:26:42 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-16 04:26:42 (9420) [INFO] Determining fastest mirrors
* 2025-02-16 04:26:45 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-16 04:26:45 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-16 04:26:45 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-16 04:26:45 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-16 04:26:45 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-16 04:26:46 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-16 04:26:46 (9420) [INFO] Trying other mirror.
* 2025-02-16 04:26:46 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-16 04:26:46 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-16 04:26:46 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-16 04:26:46 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-16 04:26:46 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-16 04:26:46 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-16 04:26:46 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-16 04:26:46 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-16 04:26:46 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-16 04:26:46 (9420) [INFO]         or
* 2025-02-16 04:26:46 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-16 04:26:46 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-16 04:26:46 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-16 04:26:46 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-16 04:26:46 (9420) [INFO]         compromise:
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-16 04:26:46 (9420) [INFO] 
* 2025-02-16 04:26:46 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-16 04:26:46 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-16 04:26:46 (9437) [INFO] 
* 2025-02-16 04:26:46 (5894) [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-16 04:26:46 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-16 04:26:46 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-16 04:26:47 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YOtJ14OhdD/ea_profile.json
* 2025-02-16 04:26:49 (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/YOtJ14OhdD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-16 04:26:49 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-17 04:25:34 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-17 04:25:35 (10486) [INFO] Script is up to date.
* 2025-02-17 04:25:36 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-17 04:25:36 (9407) [INFO] 
* 2025-02-17 04:25:39 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-17 04:25:39 (9407) [INFO] 
* 2025-02-17 04:25:46 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-17 04:25:46 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-17 04:25:46 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-17 04:25:46 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-17 04:25:46 (9407) [INFO] 
* 2025-02-17 04:25:46 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-17 04:25:47 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-17 04:25:48 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-17 04:25:48 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-17 04:25:48 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-17 04:25:48 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-17 04:25:48 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-17 04:25:49 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-17 04:25:49 (9420) [INFO] Trying other mirror.
* 2025-02-17 04:25:49 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-17 04:25:49 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-17 04:25:49 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-17 04:25:49 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-17 04:25:49 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-17 04:25:49 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-17 04:25:49 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-17 04:25:49 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-17 04:25:49 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-17 04:25:49 (9420) [INFO]         or
* 2025-02-17 04:25:49 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-17 04:25:49 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-17 04:25:49 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-17 04:25:49 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-17 04:25:49 (9420) [INFO]         compromise:
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-17 04:25:49 (9420) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-17 04:25:49 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-17 04:25:49 (9437) [INFO] 
* 2025-02-17 04:25:49 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-17 04:25:49 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-17 04:25:49 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-17 04:25:49 (9407) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-17 04:25:49 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-17 04:25:49 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-17 04:25:49 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-17 04:25:49 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-17 04:25:49 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-17 04:25:49 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-17 04:25:49 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-17 04:25:49 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-17 04:25:49 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-17 04:25:49 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-17 04:25:49 (9437) [INFO] 
* 2025-02-17 04:25:49 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-17 04:25:49 (9407) [INFO] 
* 2025-02-17 04:25:49 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-17 04:25:49 (9420) [INFO] Determining fastest mirrors
* 2025-02-17 04:25:53 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-17 04:25:53 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-17 04:25:53 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-17 04:25:53 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-17 04:25:53 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-17 04:25:54 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-17 04:25:54 (9420) [INFO] Trying other mirror.
* 2025-02-17 04:25:54 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-17 04:25:54 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-17 04:25:54 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-17 04:25:54 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-17 04:25:54 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-17 04:25:54 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-17 04:25:54 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-17 04:25:54 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-17 04:25:54 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-17 04:25:54 (9420) [INFO]         or
* 2025-02-17 04:25:54 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-17 04:25:54 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-17 04:25:54 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-17 04:25:54 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-17 04:25:54 (9420) [INFO]         compromise:
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-17 04:25:54 (9420) [INFO] 
* 2025-02-17 04:25:54 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-17 04:25:54 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-17 04:25:54 (9437) [INFO] 
* 2025-02-17 04:25:54 (5894) [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-17 04:25:54 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-17 04:25:54 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-17 04:25:55 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/znuNX_3dMM/ea_profile.json
* 2025-02-17 04:25:57 (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/znuNX_3dMM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-17 04:25:57 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-18 04:25:31 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-18 04:25:31 (10486) [INFO] Script is up to date.
* 2025-02-18 04:25:33 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-18 04:25:33 (9407) [INFO] 
* 2025-02-18 04:25:37 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-18 04:25:37 (9407) [INFO] 
* 2025-02-18 04:25:43 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-18 04:25:43 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-18 04:25:43 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-18 04:25:43 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-18 04:25:43 (9407) [INFO] 
* 2025-02-18 04:25:43 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-18 04:25:43 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-18 04:25:44 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-18 04:25:44 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-18 04:25:44 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-18 04:25:44 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-18 04:25:44 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-18 04:25:45 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-18 04:25:45 (9420) [INFO] Trying other mirror.
* 2025-02-18 04:25:45 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-18 04:25:45 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-18 04:25:45 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-18 04:25:45 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-18 04:25:45 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-18 04:25:45 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-18 04:25:45 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-18 04:25:45 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-18 04:25:45 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-18 04:25:45 (9420) [INFO]         or
* 2025-02-18 04:25:45 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-18 04:25:45 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-18 04:25:45 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-18 04:25:45 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-18 04:25:45 (9420) [INFO]         compromise:
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-18 04:25:45 (9420) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-18 04:25:45 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-18 04:25:45 (9437) [INFO] 
* 2025-02-18 04:25:45 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-18 04:25:45 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-18 04:25:45 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-18 04:25:45 (9407) [INFO] 
* 2025-02-18 04:25:45 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-18 04:25:45 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-18 04:25:45 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-18 04:25:45 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-18 04:25:45 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-18 04:25:45 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-18 04:25:45 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-18 04:25:45 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-18 04:25:45 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-18 04:25:45 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-18 04:25:45 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-18 04:25:45 (9437) [INFO] 
* 2025-02-18 04:25:45 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-18 04:25:45 (9407) [INFO] 
* 2025-02-18 04:25:46 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-18 04:25:46 (9420) [INFO] Determining fastest mirrors
* 2025-02-18 04:25:49 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-18 04:25:49 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-18 04:25:49 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-18 04:25:49 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-18 04:25:49 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-18 04:25:50 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-18 04:25:50 (9420) [INFO] Trying other mirror.
* 2025-02-18 04:25:50 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-18 04:25:50 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-18 04:25:50 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-18 04:25:50 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-18 04:25:50 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-18 04:25:50 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-18 04:25:50 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-18 04:25:50 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-18 04:25:50 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-18 04:25:50 (9420) [INFO]         or
* 2025-02-18 04:25:50 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-18 04:25:50 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-18 04:25:50 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-18 04:25:50 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-18 04:25:50 (9420) [INFO]         compromise:
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-18 04:25:50 (9420) [INFO] 
* 2025-02-18 04:25:50 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-18 04:25:50 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-18 04:25:50 (9437) [INFO] 
* 2025-02-18 04:25:50 (5894) [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-18 04:25:50 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-18 04:25:50 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-18 04:25:51 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2clHPzzch1/ea_profile.json
* 2025-02-18 04:25:53 (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/2clHPzzch1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-18 04:25:53 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-19 04:25:32 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-19 04:25:33 (10486) [INFO] Script is up to date.
* 2025-02-19 04:25:33 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-19 04:25:33 (9407) [INFO] 
* 2025-02-19 04:25:36 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-19 04:25:36 (9407) [INFO] 
* 2025-02-19 04:25:42 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-19 04:25:42 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-19 04:25:42 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-19 04:25:42 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-19 04:25:42 (9407) [INFO] 
* 2025-02-19 04:25:42 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-19 04:25:42 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-19 04:25:43 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-19 04:25:43 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-19 04:25:43 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-19 04:25:43 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-19 04:25:43 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-19 04:25:44 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-19 04:25:44 (9420) [INFO] Trying other mirror.
* 2025-02-19 04:25:44 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-19 04:25:44 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-19 04:25:44 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-19 04:25:44 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-19 04:25:44 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-19 04:25:44 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-19 04:25:44 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-19 04:25:44 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-19 04:25:44 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-19 04:25:44 (9420) [INFO]         or
* 2025-02-19 04:25:44 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-19 04:25:44 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-19 04:25:44 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-19 04:25:44 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-19 04:25:44 (9420) [INFO]         compromise:
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-19 04:25:44 (9420) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-19 04:25:44 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-19 04:25:44 (9437) [INFO] 
* 2025-02-19 04:25:44 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-19 04:25:44 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-19 04:25:44 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-19 04:25:44 (9407) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-19 04:25:44 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-19 04:25:44 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-19 04:25:44 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-19 04:25:44 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-19 04:25:44 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-19 04:25:44 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-19 04:25:44 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-19 04:25:44 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-19 04:25:44 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-19 04:25:44 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-19 04:25:44 (9437) [INFO] 
* 2025-02-19 04:25:44 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-19 04:25:44 (9407) [INFO] 
* 2025-02-19 04:25:44 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-19 04:25:44 (9420) [INFO] Determining fastest mirrors
* 2025-02-19 04:25:47 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-19 04:25:47 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-19 04:25:47 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-19 04:25:47 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-19 04:25:47 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-19 04:25:48 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-19 04:25:48 (9420) [INFO] Trying other mirror.
* 2025-02-19 04:25:48 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-19 04:25:48 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-19 04:25:48 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-19 04:25:48 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-19 04:25:48 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-19 04:25:48 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-19 04:25:48 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-19 04:25:48 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-19 04:25:48 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-19 04:25:48 (9420) [INFO]         or
* 2025-02-19 04:25:48 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-19 04:25:48 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-19 04:25:48 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-19 04:25:48 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-19 04:25:48 (9420) [INFO]         compromise:
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-19 04:25:48 (9420) [INFO] 
* 2025-02-19 04:25:48 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-19 04:25:48 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-19 04:25:48 (9437) [INFO] 
* 2025-02-19 04:25:48 (5894) [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-19 04:25:48 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-19 04:25:48 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-19 04:25:49 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dOX3UIbNXK/ea_profile.json
* 2025-02-19 04:25:51 (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/dOX3UIbNXK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-19 04:25:51 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-20 04:25:36 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-20 04:25:36 (10486) [INFO] Script is up to date.
* 2025-02-20 04:25:39 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-20 04:25:39 (9407) [INFO] 
* 2025-02-20 04:25:43 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-20 04:25:43 (9407) [INFO] 
* 2025-02-20 04:25:48 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-20 04:25:48 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-20 04:25:48 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-20 04:25:49 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-20 04:25:49 (9407) [INFO] 
* 2025-02-20 04:25:49 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-20 04:25:49 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-20 04:25:51 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-20 04:25:51 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-20 04:25:51 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-20 04:25:51 (9420) [INFO]  * epel: dl.fedoraproject.org
* 2025-02-20 04:25:51 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-20 04:25:52 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-20 04:25:52 (9420) [INFO] Trying other mirror.
* 2025-02-20 04:25:52 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-20 04:25:52 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-20 04:25:52 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-20 04:25:52 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-20 04:25:52 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-20 04:25:52 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-20 04:25:52 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-20 04:25:52 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-20 04:25:52 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-20 04:25:52 (9420) [INFO]         or
* 2025-02-20 04:25:52 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-20 04:25:52 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-20 04:25:52 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-20 04:25:52 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-20 04:25:52 (9420) [INFO]         compromise:
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-20 04:25:52 (9420) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-20 04:25:52 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-20 04:25:52 (9437) [INFO] 
* 2025-02-20 04:25:52 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-20 04:25:52 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-20 04:25:52 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-20 04:25:52 (9407) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-20 04:25:52 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-20 04:25:52 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-20 04:25:52 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-20 04:25:52 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-20 04:25:52 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-20 04:25:52 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-20 04:25:52 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-20 04:25:52 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-20 04:25:52 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-20 04:25:52 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-20 04:25:52 (9437) [INFO] 
* 2025-02-20 04:25:52 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-20 04:25:52 (9407) [INFO] 
* 2025-02-20 04:25:52 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-20 04:25:53 (9420) [INFO] Determining fastest mirrors
* 2025-02-20 04:25:56 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-20 04:25:56 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-20 04:25:56 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-20 04:25:56 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-20 04:25:56 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-20 04:25:57 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-20 04:25:57 (9420) [INFO] Trying other mirror.
* 2025-02-20 04:25:57 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-20 04:25:57 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-20 04:25:57 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-20 04:25:57 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-20 04:25:57 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-20 04:25:57 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-20 04:25:57 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-20 04:25:57 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-20 04:25:57 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-20 04:25:57 (9420) [INFO]         or
* 2025-02-20 04:25:57 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-20 04:25:57 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-20 04:25:57 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-20 04:25:57 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-20 04:25:57 (9420) [INFO]         compromise:
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-20 04:25:57 (9420) [INFO] 
* 2025-02-20 04:25:57 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-20 04:25:57 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-20 04:25:57 (9437) [INFO] 
* 2025-02-20 04:25:57 (5894) [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-20 04:25:57 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-20 04:25:57 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-20 04:25:58 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0DItXCEOsK/ea_profile.json
* 2025-02-20 04:26:01 (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/0DItXCEOsK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-20 04:26:01 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-21 04:25:34 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-21 04:25:34 (10486) [INFO] Script is up to date.
* 2025-02-21 04:25:36 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-21 04:25:36 (9407) [INFO] 
* 2025-02-21 04:25:39 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-21 04:25:39 (9407) [INFO] 
* 2025-02-21 04:25:45 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-21 04:25:45 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-21 04:25:45 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-21 04:25:45 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-21 04:25:45 (9407) [INFO] 
* 2025-02-21 04:25:45 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-21 04:25:45 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-21 04:25:46 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-21 04:25:46 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-21 04:25:46 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-21 04:25:46 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-21 04:25:46 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-21 04:25:46 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-21 04:25:46 (9420) [INFO] Trying other mirror.
* 2025-02-21 04:25:46 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-21 04:25:46 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-21 04:25:46 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-21 04:25:46 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-21 04:25:46 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-21 04:25:46 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-21 04:25:46 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-21 04:25:46 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-21 04:25:46 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-21 04:25:46 (9420) [INFO]         or
* 2025-02-21 04:25:46 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-21 04:25:46 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-21 04:25:46 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-21 04:25:46 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-21 04:25:46 (9420) [INFO]         compromise:
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-21 04:25:46 (9420) [INFO] 
* 2025-02-21 04:25:46 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-21 04:25:46 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-21 04:25:47 (9437) [INFO] 
* 2025-02-21 04:25:47 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-21 04:25:47 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-21 04:25:47 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-21 04:25:47 (9407) [INFO] 
* 2025-02-21 04:25:47 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-21 04:25:47 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-21 04:25:47 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-21 04:25:47 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-21 04:25:47 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-21 04:25:47 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-21 04:25:47 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-21 04:25:47 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-21 04:25:47 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-21 04:25:47 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-21 04:25:47 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-21 04:25:47 (9437) [INFO] 
* 2025-02-21 04:25:47 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-21 04:25:47 (9407) [INFO] 
* 2025-02-21 04:25:47 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-21 04:25:47 (9420) [INFO] Determining fastest mirrors
* 2025-02-21 04:25:50 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-21 04:25:50 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-21 04:25:50 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-21 04:25:50 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-21 04:25:50 (9420) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-02-21 04:25:51 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-21 04:25:51 (9420) [INFO] Trying other mirror.
* 2025-02-21 04:25:51 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-21 04:25:51 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-21 04:25:51 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-21 04:25:51 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-21 04:25:51 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-21 04:25:51 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-21 04:25:51 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-21 04:25:51 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-21 04:25:51 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-21 04:25:51 (9420) [INFO]         or
* 2025-02-21 04:25:51 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-21 04:25:51 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-21 04:25:51 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-21 04:25:51 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-21 04:25:51 (9420) [INFO]         compromise:
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-21 04:25:51 (9420) [INFO] 
* 2025-02-21 04:25:51 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-21 04:25:51 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-21 04:25:51 (9437) [INFO] 
* 2025-02-21 04:25:51 (5894) [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-21 04:25:51 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-21 04:25:51 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-21 04:25:52 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RQJTT5Oapp/ea_profile.json
* 2025-02-21 04:25:54 (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/RQJTT5Oapp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-21 04:25:54 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-22 04:26:24 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-22 04:26:24 (10486) [INFO] Script is up to date.
* 2025-02-22 04:26:25 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-22 04:26:25 (9407) [INFO] 
* 2025-02-22 04:26:28 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-22 04:26:28 (9407) [INFO] 
* 2025-02-22 04:26:37 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-22 04:26:37 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-22 04:26:37 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-22 04:26:37 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-22 04:26:37 (9407) [INFO] 
* 2025-02-22 04:26:37 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-22 04:26:37 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-22 04:26:38 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-22 04:26:38 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-22 04:26:38 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-22 04:26:38 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-22 04:26:38 (9420) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-02-22 04:26:38 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-22 04:26:38 (9420) [INFO] Trying other mirror.
* 2025-02-22 04:26:38 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-22 04:26:38 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-22 04:26:38 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-22 04:26:38 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-22 04:26:38 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-22 04:26:38 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-22 04:26:38 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-22 04:26:38 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-22 04:26:38 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-22 04:26:38 (9420) [INFO]         or
* 2025-02-22 04:26:38 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-22 04:26:38 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-22 04:26:38 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-22 04:26:38 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-22 04:26:38 (9420) [INFO]         compromise:
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-22 04:26:38 (9420) [INFO] 
* 2025-02-22 04:26:38 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-22 04:26:38 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-22 04:26:38 (9437) [INFO] 
* 2025-02-22 04:26:38 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-22 04:26:38 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-22 04:26:38 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-22 04:26:38 (9407) [INFO] 
* 2025-02-22 04:26:39 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-22 04:26:39 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-22 04:26:39 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-22 04:26:39 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-22 04:26:39 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-22 04:26:39 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-22 04:26:39 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-22 04:26:39 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-22 04:26:39 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-22 04:26:39 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-22 04:26:39 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-22 04:26:39 (9437) [INFO] 
* 2025-02-22 04:26:39 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-22 04:26:39 (9407) [INFO] 
* 2025-02-22 04:26:39 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-22 04:26:39 (9420) [INFO] Determining fastest mirrors
* 2025-02-22 04:26:44 (9420) [INFO]  * EA4: 63.247.64.58
* 2025-02-22 04:26:44 (9420) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-02-22 04:26:44 (9420) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-02-22 04:26:44 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-22 04:26:44 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-22 04:26:44 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-22 04:26:44 (9420) [INFO] Trying other mirror.
* 2025-02-22 04:26:44 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-22 04:26:44 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-22 04:26:44 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-22 04:26:44 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-22 04:26:44 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-22 04:26:44 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-22 04:26:44 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-22 04:26:44 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-22 04:26:44 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-22 04:26:44 (9420) [INFO]         or
* 2025-02-22 04:26:44 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-22 04:26:44 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-22 04:26:44 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-22 04:26:44 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-22 04:26:44 (9420) [INFO]         compromise:
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-22 04:26:44 (9420) [INFO] 
* 2025-02-22 04:26:44 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-22 04:26:44 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-22 04:26:44 (9437) [INFO] 
* 2025-02-22 04:26:44 (5894) [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-22 04:26:44 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-22 04:26:45 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-22 04:26:45 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PUFXb505mj/ea_profile.json
* 2025-02-22 04:26:47 (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/PUFXb505mj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-22 04:26:47 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-23 04:26:14 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-23 04:26:14 (10486) [INFO] Script is up to date.
* 2025-02-23 04:26:16 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-23 04:26:16 (9407) [INFO] 
* 2025-02-23 04:26:18 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-23 04:26:18 (9407) [INFO] 
* 2025-02-23 04:26:25 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-23 04:26:25 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-23 04:26:25 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-23 04:26:25 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-23 04:26:25 (9407) [INFO] 
* 2025-02-23 04:26:25 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-23 04:26:25 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-23 04:26:26 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-23 04:26:26 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-23 04:26:26 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-23 04:26:26 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-23 04:26:26 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-23 04:26:27 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-23 04:26:27 (9420) [INFO] Trying other mirror.
* 2025-02-23 04:26:27 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-23 04:26:27 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-23 04:26:27 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-23 04:26:27 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-23 04:26:27 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-23 04:26:27 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-23 04:26:27 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-23 04:26:27 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-23 04:26:27 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-23 04:26:27 (9420) [INFO]         or
* 2025-02-23 04:26:27 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-23 04:26:27 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-23 04:26:27 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-23 04:26:27 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-23 04:26:27 (9420) [INFO]         compromise:
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-23 04:26:27 (9420) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-23 04:26:27 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-23 04:26:27 (9437) [INFO] 
* 2025-02-23 04:26:27 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-23 04:26:27 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-23 04:26:27 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-23 04:26:27 (9407) [INFO] 
* 2025-02-23 04:26:27 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-23 04:26:27 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-23 04:26:27 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-23 04:26:27 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-23 04:26:27 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-23 04:26:27 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-23 04:26:27 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-23 04:26:27 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-23 04:26:27 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-23 04:26:27 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-23 04:26:27 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-23 04:26:28 (9437) [INFO] 
* 2025-02-23 04:26:28 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-23 04:26:28 (9407) [INFO] 
* 2025-02-23 04:26:28 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-23 04:26:28 (9420) [INFO] Determining fastest mirrors
* 2025-02-23 04:26:33 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-23 04:26:33 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-23 04:26:33 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-23 04:26:33 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-23 04:26:33 (9420) [INFO]  * remi-safe: muug.ca
* 2025-02-23 04:26:34 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-23 04:26:34 (9420) [INFO] Trying other mirror.
* 2025-02-23 04:26:34 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-23 04:26:34 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-23 04:26:34 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-23 04:26:34 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-23 04:26:34 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-23 04:26:34 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-23 04:26:34 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-23 04:26:34 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-23 04:26:34 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-23 04:26:34 (9420) [INFO]         or
* 2025-02-23 04:26:34 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-23 04:26:34 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-23 04:26:34 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-23 04:26:34 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-23 04:26:34 (9420) [INFO]         compromise:
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-23 04:26:34 (9420) [INFO] 
* 2025-02-23 04:26:34 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-23 04:26:34 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-23 04:26:34 (9437) [INFO] 
* 2025-02-23 04:26:34 (5894) [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-23 04:26:34 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-23 04:26:34 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-23 04:26:35 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LPh0ZSplww/ea_profile.json
* 2025-02-23 04:26:38 (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/LPh0ZSplww/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-23 04:26:38 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-24 04:25:36 (10464) [INFO] Self-update of script version 61 requested.
* 2025-02-24 04:25:36 (10486) [INFO] Script is up to date.
* 2025-02-24 04:25:39 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-24 04:25:39 (9407) [INFO] 
* 2025-02-24 04:25:42 (9406) [INFO] Running: /usr/bin/yum list extras
* 2025-02-24 04:25:42 (9407) [INFO] 
* 2025-02-24 04:25:49 (6001) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-02-24 04:25:49 (6001) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-02-24 04:25:49 (6025) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-02-24 04:25:49 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-24 04:25:49 (9407) [INFO] 
* 2025-02-24 04:25:49 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-24 04:25:49 (9420) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-24 04:25:50 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-24 04:25:50 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-24 04:25:50 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-24 04:25:50 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-24 04:25:50 (9420) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-02-24 04:25:50 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-24 04:25:50 (9420) [INFO] Trying other mirror.
* 2025-02-24 04:25:50 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-24 04:25:50 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-24 04:25:50 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-24 04:25:50 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-24 04:25:50 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-24 04:25:50 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-24 04:25:50 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-24 04:25:50 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-24 04:25:50 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-24 04:25:50 (9420) [INFO]         or
* 2025-02-24 04:25:50 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-24 04:25:50 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-24 04:25:50 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-24 04:25:50 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-24 04:25:50 (9420) [INFO]         compromise:
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-24 04:25:50 (9420) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-24 04:25:50 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-24 04:25:50 (9437) [INFO] 
* 2025-02-24 04:25:50 (5884) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-24 04:25:50 (5885) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-24 04:25:50 (9406) [INFO] Running: /usr/bin/yum clean all
* 2025-02-24 04:25:50 (9407) [INFO] 
* 2025-02-24 04:25:50 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-24 04:25:51 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-02-24 04:25:51 (9420) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-24 04:25:51 (9420) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-24 04:25:51 (9420) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-02-24 04:25:51 (9420) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-02-24 04:25:51 (9420) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-02-24 04:25:51 (9420) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-02-24 04:25:51 (9420) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-02-24 04:25:51 (9420) [INFO] Cleaning up list of fastest mirrors
* 2025-02-24 04:25:51 (9420) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-02-24 04:25:51 (9437) [INFO] 
* 2025-02-24 04:25:51 (9406) [INFO] Running: /usr/bin/yum makecache
* 2025-02-24 04:25:51 (9407) [INFO] 
* 2025-02-24 04:25:51 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-24 04:25:51 (9420) [INFO] Determining fastest mirrors
* 2025-02-24 04:25:54 (9420) [INFO]  * EA4: 185.125.185.32
* 2025-02-24 04:25:54 (9420) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-24 04:25:54 (9420) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-24 04:25:54 (9420) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-24 04:25:54 (9420) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-24 04:25:55 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-24 04:25:55 (9420) [INFO] Trying other mirror.
* 2025-02-24 04:25:55 (9420) [INFO] To address this issue please refer to the below wiki article 
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO] https://wiki.centos.org/yum-errors
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-02-24 04:25:55 (9420) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-24 04:25:55 (9420) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-24 04:25:55 (9420) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-24 04:25:55 (9420) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-24 04:25:55 (9420) [INFO]         packages for the previous distribution release still work).
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-24 04:25:55 (9420) [INFO]             yum --disablerepo=base ...
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-24 04:25:55 (9420) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-24 04:25:55 (9420) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO]             yum-config-manager --disable base
* 2025-02-24 04:25:55 (9420) [INFO]         or
* 2025-02-24 04:25:55 (9420) [INFO]             subscription-manager repos --disable=base
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-24 04:25:55 (9420) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-24 04:25:55 (9420) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-24 04:25:55 (9420) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-24 04:25:55 (9420) [INFO]         compromise:
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-02-24 04:25:55 (9420) [INFO] 
* 2025-02-24 04:25:55 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-02-24 04:25:55 (9420) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-24 04:25:55 (9437) [INFO] 
* 2025-02-24 04:25:55 (5894) [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-24 04:25:55 (5895) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-02-24 04:25:55 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-24 04:25:56 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TJhuQfHMIw/ea_profile.json
* 2025-02-24 04:25:57 (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/TJhuQfHMIw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533.
* 2025-02-24 04:25:57 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-06-11 04:25:40 (10464) [INFO] Self-update of script version 61 requested.
* 2025-06-11 04:25:40 (10469) [INFO] Newer version of script found. Downloading.
* 2025-06-11 04:25:41 (10478) [INFO] Script update to version 66 successful.
* 2025-06-11 04:25:42 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only
* 2025-06-11 04:25:42 (10169) [INFO] 
* 2025-06-11 04:26:30 (10199) [INFO] 
* 2025-06-11 04:26:30 (259) [ERROR] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.51) does not appear to be up to date.
Please upgrade cPanel to 11.110.0.67.

* 2025-06-11 04:26:30 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-06-11 04:26:30 (10169) [INFO] 
* 2025-06-11 04:26:34 (10168) [INFO] Running: /usr/bin/yum list extras
* 2025-06-11 04:26:34 (10169) [INFO] 
* 2025-06-11 04:26:38 (6504) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-06-11 04:26:38 (6504) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-06-11 04:26:38 (6528) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-06-11 04:26:38 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-11 04:26:38 (10169) [INFO] 
* 2025-06-11 04:26:38 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-11 04:26:39 (10182) [INFO] Loading mirror speeds from cached hostfile
* 2025-06-11 04:26:40 (10182) [INFO]  * EA4: 184.94.196.97
* 2025-06-11 04:26:40 (10182) [INFO]  * cpanel-addons-production-feed: 184.94.196.97
* 2025-06-11 04:26:40 (10182) [INFO]  * cpanel-plugins: 184.94.196.97
* 2025-06-11 04:26:40 (10182) [INFO]  * epel: mirror.math.princeton.edu
* 2025-06-11 04:26:40 (10182) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-06-11 04:26:41 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-11 04:26:41 (10182) [INFO] Trying other mirror.
* 2025-06-11 04:26:41 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-06-11 04:26:41 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-11 04:26:41 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-11 04:26:41 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-11 04:26:41 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-11 04:26:41 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-11 04:26:41 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-11 04:26:41 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-11 04:26:41 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-11 04:26:41 (10182) [INFO]         or
* 2025-06-11 04:26:41 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-11 04:26:41 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-11 04:26:41 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-11 04:26:41 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-11 04:26:41 (10182) [INFO]         compromise:
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-11 04:26:41 (10182) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-11 04:26:41 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-11 04:26:41 (10199) [INFO] 
* 2025-06-11 04:26:41 (6386) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-11 04:26:41 (6387) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-06-11 04:26:41 (10168) [INFO] Running: /usr/bin/yum clean all
* 2025-06-11 04:26:41 (10169) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-11 04:26:41 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-06-11 04:26:41 (10182) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-06-11 04:26:41 (10182) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-06-11 04:26:41 (10182) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-06-11 04:26:41 (10182) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-06-11 04:26:41 (10182) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-06-11 04:26:41 (10182) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-06-11 04:26:41 (10182) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-06-11 04:26:41 (10182) [INFO] Cleaning up list of fastest mirrors
* 2025-06-11 04:26:41 (10182) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-06-11 04:26:41 (10199) [INFO] 
* 2025-06-11 04:26:41 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-11 04:26:41 (10169) [INFO] 
* 2025-06-11 04:26:41 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-11 04:26:42 (10182) [INFO] Determining fastest mirrors
* 2025-06-11 04:26:44 (10182) [INFO]  * EA4: 63.247.64.58
* 2025-06-11 04:26:44 (10182) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-06-11 04:26:44 (10182) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-06-11 04:26:44 (10182) [INFO]  * epel: mirror.math.princeton.edu
* 2025-06-11 04:26:44 (10182) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-06-11 04:26:44 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-11 04:26:44 (10182) [INFO] Trying other mirror.
* 2025-06-11 04:26:44 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-06-11 04:26:44 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-11 04:26:44 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-11 04:26:44 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-11 04:26:44 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-11 04:26:44 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-11 04:26:44 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-11 04:26:44 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-11 04:26:44 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-11 04:26:44 (10182) [INFO]         or
* 2025-06-11 04:26:44 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-11 04:26:44 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-11 04:26:44 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-11 04:26:44 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-11 04:26:44 (10182) [INFO]         compromise:
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-11 04:26:44 (10182) [INFO] 
* 2025-06-11 04:26:44 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-11 04:26:44 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-11 04:26:44 (10199) [INFO] 
* 2025-06-11 04:26:44 (6396) [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-06-11 04:26:44 (6397) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-11 04:26:45 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-06-11 04:26:46 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZJqdHW_2AI/ea_profile.json
* 2025-06-11 04:26:48 (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/ZJqdHW_2AI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290.
* 2025-06-11 04:26:48 (476) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-06-12 04:25:36 (11230) [INFO] Self-update of script version 66 requested.
* 2025-06-12 04:25:37 (11252) [INFO] Script is up to date.
* 2025-06-12 04:25:38 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only
* 2025-06-12 04:25:38 (10169) [INFO] 
* 2025-06-12 04:26:19 (10199) [INFO] 
* 2025-06-12 04:26:19 (259) [ERROR] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.51) does not appear to be up to date.
Additionally, we were unable to determine the expected version for this build.

* 2025-06-12 04:26:19 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-06-12 04:26:19 (10169) [INFO] 
* 2025-06-12 04:26:22 (10168) [INFO] Running: /usr/bin/yum list extras
* 2025-06-12 04:26:22 (10169) [INFO] 
* 2025-06-12 04:26:27 (6504) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-06-12 04:26:27 (6504) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-06-12 04:26:27 (6528) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-06-12 04:26:27 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-12 04:26:27 (10169) [INFO] 
* 2025-06-12 04:26:27 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-12 04:26:27 (10182) [INFO] Loading mirror speeds from cached hostfile
* 2025-06-12 04:26:28 (10182) [INFO]  * EA4: 63.247.64.58
* 2025-06-12 04:26:28 (10182) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-06-12 04:26:28 (10182) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-06-12 04:26:28 (10182) [INFO]  * epel: mirror.math.princeton.edu
* 2025-06-12 04:26:28 (10182) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-06-12 04:26:29 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 04:26:29 (10182) [INFO] Trying other mirror.
* 2025-06-12 04:26:29 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-06-12 04:26:29 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-12 04:26:29 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-12 04:26:29 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-12 04:26:29 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-12 04:26:29 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-12 04:26:29 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-12 04:26:29 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-12 04:26:29 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-12 04:26:29 (10182) [INFO]         or
* 2025-06-12 04:26:29 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-12 04:26:29 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-12 04:26:29 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-12 04:26:29 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-12 04:26:29 (10182) [INFO]         compromise:
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-12 04:26:29 (10182) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-12 04:26:29 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 04:26:29 (10199) [INFO] 
* 2025-06-12 04:26:29 (6386) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 04:26:29 (6387) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-06-12 04:26:29 (10168) [INFO] Running: /usr/bin/yum clean all
* 2025-06-12 04:26:29 (10169) [INFO] 
* 2025-06-12 04:26:29 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-12 04:26:29 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-06-12 04:26:29 (10182) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-06-12 04:26:29 (10182) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-06-12 04:26:29 (10182) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-06-12 04:26:29 (10182) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-06-12 04:26:29 (10182) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-06-12 04:26:29 (10182) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-06-12 04:26:29 (10182) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-06-12 04:26:29 (10182) [INFO] Cleaning up list of fastest mirrors
* 2025-06-12 04:26:29 (10182) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-06-12 04:26:29 (10199) [INFO] 
* 2025-06-12 04:26:29 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-12 04:26:29 (10169) [INFO] 
* 2025-06-12 04:26:30 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-12 04:26:30 (10182) [INFO] Determining fastest mirrors
* 2025-06-12 04:26:32 (10182) [INFO]  * EA4: 63.247.64.58
* 2025-06-12 04:26:32 (10182) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-06-12 04:26:32 (10182) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-06-12 04:26:32 (10182) [INFO]  * epel: mirror.math.princeton.edu
* 2025-06-12 04:26:32 (10182) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-06-12 04:26:32 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 04:26:32 (10182) [INFO] Trying other mirror.
* 2025-06-12 04:26:32 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-06-12 04:26:32 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-12 04:26:32 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-12 04:26:32 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-12 04:26:32 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-12 04:26:32 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-12 04:26:32 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-12 04:26:32 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-12 04:26:32 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-12 04:26:32 (10182) [INFO]         or
* 2025-06-12 04:26:32 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-12 04:26:32 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-12 04:26:32 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-12 04:26:32 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-12 04:26:32 (10182) [INFO]         compromise:
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-12 04:26:32 (10182) [INFO] 
* 2025-06-12 04:26:32 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-12 04:26:32 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 04:26:32 (10199) [INFO] 
* 2025-06-12 04:26:32 (6396) [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-06-12 04:26:32 (6397) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 04:26:33 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-06-12 04:26:33 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B_n1ackpIW/ea_profile.json
* 2025-06-12 04:26:36 (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/B_n1ackpIW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290.
* 2025-06-12 04:26:36 (476) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-06-13 04:25:35 (11230) [INFO] Self-update of script version 66 requested.
* 2025-06-13 04:25:35 (11252) [INFO] Script is up to date.
* 2025-06-13 04:25:36 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only
* 2025-06-13 04:25:36 (10169) [INFO] 
* 2025-06-13 04:26:18 (10199) [INFO] 
* 2025-06-13 04:26:18 (259) [ERROR] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.51) does not appear to be up to date.
Please upgrade cPanel to 11.110.0.68.

* 2025-06-13 04:26:18 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-06-13 04:26:18 (10169) [INFO] 
* 2025-06-13 04:26:21 (10168) [INFO] Running: /usr/bin/yum list extras
* 2025-06-13 04:26:21 (10169) [INFO] 
* 2025-06-13 04:26:25 (6504) [ERROR] 1 package(s) installed from unsupported YUM repo 'remi-safe' from /etc/yum.repos.d/remi-safe.repo
* 2025-06-13 04:26:25 (6504) [ERROR] 2 package(s) installed from unsupported YUM repo 'zabbix' from /etc/yum.repos.d/zabbix.repo
* 2025-06-13 04:26:25 (6528) [INFO] Unsupported YUM repo enabled 'zabbix-non-supported' without packages installed from /etc/yum.repos.d/zabbix.repo, these will be disabled before ELevation
* 2025-06-13 04:26:25 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-13 04:26:25 (10169) [INFO] 
* 2025-06-13 04:26:25 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-13 04:26:26 (10182) [INFO] Loading mirror speeds from cached hostfile
* 2025-06-13 04:26:27 (10182) [INFO]  * EA4: 63.247.64.58
* 2025-06-13 04:26:27 (10182) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-06-13 04:26:27 (10182) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-06-13 04:26:27 (10182) [INFO]  * epel: mirror.math.princeton.edu
* 2025-06-13 04:26:27 (10182) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-06-13 04:26:27 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 04:26:27 (10182) [INFO] Trying other mirror.
* 2025-06-13 04:26:28 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-06-13 04:26:28 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-13 04:26:28 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-13 04:26:28 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-13 04:26:28 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-13 04:26:28 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-13 04:26:28 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-13 04:26:28 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-13 04:26:28 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-13 04:26:28 (10182) [INFO]         or
* 2025-06-13 04:26:28 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-13 04:26:28 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-13 04:26:28 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-13 04:26:28 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-13 04:26:28 (10182) [INFO]         compromise:
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-13 04:26:28 (10182) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-13 04:26:28 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 04:26:28 (10199) [INFO] 
* 2025-06-13 04:26:28 (6386) [WARN] Initial run of "yum makecache" failed: http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 04:26:28 (6387) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-06-13 04:26:28 (10168) [INFO] Running: /usr/bin/yum clean all
* 2025-06-13 04:26:28 (10169) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-13 04:26:28 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2025-06-13 04:26:28 (10182) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-06-13 04:26:28 (10182) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-06-13 04:26:28 (10182) [INFO]               : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1
* 2025-06-13 04:26:28 (10182) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2025-06-13 04:26:28 (10182) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2025-06-13 04:26:28 (10182) [INFO]               : imunify360-rollout-8 remi-safe updates wp-toolkit-cpanel
* 2025-06-13 04:26:28 (10182) [INFO]               : wp-toolkit-thirdparties zabbix zabbix-non-supported
* 2025-06-13 04:26:28 (10182) [INFO] Cleaning up list of fastest mirrors
* 2025-06-13 04:26:28 (10182) [INFO] Other repos take up 4.2 M of disk space (use --verbose for details)
* 2025-06-13 04:26:28 (10199) [INFO] 
* 2025-06-13 04:26:28 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-13 04:26:28 (10169) [INFO] 
* 2025-06-13 04:26:28 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-13 04:26:28 (10182) [INFO] Determining fastest mirrors
* 2025-06-13 04:26:31 (10182) [INFO]  * EA4: 63.247.64.58
* 2025-06-13 04:26:31 (10182) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2025-06-13 04:26:31 (10182) [INFO]  * cpanel-plugins: 63.247.64.58
* 2025-06-13 04:26:31 (10182) [INFO]  * epel: mirror.math.princeton.edu
* 2025-06-13 04:26:31 (10182) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-06-13 04:26:32 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 04:26:32 (10182) [INFO] Trying other mirror.
* 2025-06-13 04:26:32 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO]  One of the configured repositories failed (CentOS-7 - Base),
* 2025-06-13 04:26:32 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-13 04:26:32 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-13 04:26:32 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-13 04:26:32 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-13 04:26:32 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-13 04:26:32 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-13 04:26:32 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-13 04:26:32 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-13 04:26:32 (10182) [INFO]         or
* 2025-06-13 04:26:32 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-13 04:26:32 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-13 04:26:32 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-13 04:26:32 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-13 04:26:32 (10182) [INFO]         compromise:
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-13 04:26:32 (10182) [INFO] 
* 2025-06-13 04:26:32 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-13 04:26:32 (10182) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 04:26:32 (10199) [INFO] 
* 2025-06-13 04:26:32 (6396) [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-06-13 04:26:32 (6397) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 04:26:32 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-06-13 04:26:33 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TxaVrmVgNm/ea_profile.json
* 2025-06-13 04:26:35 (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/TxaVrmVgNm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290.
* 2025-06-13 04:26:35 (476) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/

haha - 2025